Area | Status |
---|
Community | |
Management | |
Security | |
Building & Quality | |
Packaging | |
Releases | |
Watch a video about packages, development environment and self-deployment
Now with General Bots you can press F5 on Visual Studio to get a bot factory on your environment published on November 10th, 2018.
General Bot is a package based chat bot server focused in convention over configuration and code-less approaches, which brings software packages and application server concepts to help parallel bot development.
In this MSDN article you can have an overview of a General Bots application.
Checkout our FREE Intranet Quickstart Bot
What is a Bot Server?
Bot Server accelerates the process of developing a bot. It provisions all code
base, resources and deployment to the cloud, and gives you templates you can
choose from whenever you need a new bot. The server has a database and service
backend allowing you to further modify your bot package directly by downloading
a zip file, editing and uploading it back to the server (deploying process) with
no code. The Bot Server also provides a framework to develop bot packages in a more
advanced fashion writing custom code in editors like Visual Studio Code, Atom or Brackets.
Everyone can create bots by just copying and pasting some files and using their
favorite tools like Excel (or any text editor) or Photoshop (or any image
editor).
Package Quick Reference
The same build process for everyone
GeneralBots aims to delivery bots in azure in a very easy and fast fashion. Use
Office tools like Word or Excel to edit your Bot - using code (JavaScript or TypeScript) just to empower custom requirements.
Use Excel for (Hierarchical) Knowledge Base Editing
Use Visual Studio for a complete .gbai package building system
How To
Run the server locally
- Install Node.js the current generation General Bot code execution platform;
- Open a Terminal on Linux and Mac or a Command Prompt window on Windows;
- Type
npm install -g botserver
and press ENTER; - Type
gbot
to run the server core.
Notes:
Configure the server to deploy specific directory
- Create/Edit the .env file and add the ADDITIONAL_DEPLOY_PATH key pointing to the .gbai local parent folder of .gbapp, .gbot, .gbtheme, .gbkb package directories.
- Specify STORAGE_SYNC to TRUE so database sync is run when the server is run.
- In case of Microsoft SQL Server add the following keys: STORAGE_SERVER, STORAGE_NAME, STORAGE_USERNAME, STORAGE_PASSWORD, STORAGE_DIALECT to
mssql
.
Note:
- You can specify several bots separated by semicolon, the BotServer will serve all of them at once.
Setup development environment (Windows)
- [Optional] Install Chocolatey, a Windows Package Manager;
- Install git, a Software Configuration Management (SCM).;
- Install Node.js, a Runtime system.
(https://www.npmjs.com/get-npm) (suggested: LTS 8.x.x);
- Install Visual Studio Code, Brackets or Atom as an editor of your choice;
- Fork by visiting https://github.com/pragmatismo-io/BotServer/fork
- Clone the just forked repository by running
git clone <your-forked-repository-url>/BotServer.git
; - Run
npm install -g typescript
; - Run
npm install
on Command Prompt or PowerShell on the General Bot source-code folder; - Enter './packages/default.gbui' folder;
- Run
npm install
folled by npm run build
(To build default Bot UI); - Enter the On the downloaded folder (../..);
- Compile the bot server by
tsc
. - Run the bot server by
npm start
.
Note:
- Whenever you are ready to turn your open-source bot ideas in form of .gbapp (source-code) and artifacts like .gbkb, .gbtheme, .gbot or the .gbai full package read CONTRIBUTING.md about performing Pull Requests (PR) and creating other public custom packages repositories of your own personal or organization General Bot Community Edition powered packages.
Running unit tests
- Enter the BotServer root folder.
- Run tests by
npm test
.
Just copy the source code to your machine
- [Download] the Zip file of (https://codeload.github.com/pragmatismo-io/BotServer/zip/master)
Updating the Bot Knoledge Base (.gbkb folder)
The subjects.json file contains all information related to the subject tree and can be used to build the menu carrousel as well give a set of words to be used as subject catcher in the conversation. A hierarchy can be specified.
Creating a new Theme folder (.gbtheme folder)
A theme is composed of some CSS files and images. That set of files can change
everything in the General Bot UI. Use them extensively before going to change
the UI application itself (HTML & JS).
Package Types
.gbai
Embraces all packages types (content, logic & conversation) into a pluggable bot
directory. A sample .gbai is available.
.gbapp
The artificial intelligence extensions in form of pluggable apps. Dialogs,
Services and all model related to data. A set of interactions, use cases,
integrations in form of conversationals dialogs.
The .gbapp adds the General Bot base library (botlib) for building Node.js TypeScript Apps packages.
Four components builds up a General Bot App:
- dialogs
- models
- services
- tests
Dialogs
All code contained in a dialog builds the flow to custom conversations in
built-in and additional packages .
Models
Models builds the foundation of data relationships in form of entities.
Services
Services are a façade for bot back-end logic and other custom processing.
Tests
Tests try to automate code execution validation before crashing in production.
.gbot
An expression of an artificial inteligence entity. A .gbot file defines
all bots dependencies related to services and other resources.
.gbtheme
A theme of a bot at a given time. CSS files & images that can compose all UI
presentation and using it a branding can be done. A sample .gbtheme is available
.gbkb
A set of subjects that bot knows in a form of hierarchical menu-based QnA. A sample .gbkb is available.
.gblib
Shared code that can be used across bot apps.
Reference
GeneralBots admin commands
General Bot can be controlled by the same chat window people talk to, so
here is a list of admin commands related to deploying .gb* files.
Command | Description |
---|
deployPackage | Deploy a KB package. Usage deployPackage [package-name]. Then, you need to run rebuildIndex. |
undeployPackage | Undeploy a KB. Usage undeployPackage [package-name]. |
redeployPackage | Undeploy and then deploys the KB. Usage redeployPackage [package-name]. Then, you need to run rebuildIndex. |
setupSecurity | Setup connection to user directories. |
Discontinued commands:
Command | Description | Reason |
---|
rebuildIndex | Rebuild Azure Search indexes, must be run after deployPackage or redeployPackage. | Now it is called automatically |
Credits & Inspiration
Powered by Microsoft BOT Framework and Azure.
General Bot Code Name is Guaribas, the name of a city in Brasil, state of Piaui.
Roberto Mangabeira Unger: "No one should have to do work that can be done by a machine".
Contributing
This project welcomes contributions and suggestions.
See our Contribution Guidelines for more details.
Reporting Security Issues
Security issues and bugs should be reported privately, via email, to the Pragmatismo.io Security
team at security@pragmatismo.io. You should
receive a response within 24 hours. If for some reason you do not, please follow up via
email to ensure we received your original message.
License & Warranty
General Bot Copyright (c) Pragmatismo.io. All rights reserved.
Licensed under the AGPL-3.0.
According to our dual licensing model, this program can be used either
under the terms of the GNU Affero General Public License, version 3,
or under a proprietary license.
The texts of the GNU Affero General Public License with an additional
permission and of our proprietary license can be found at and
in the LICENSE file you have received along with this program.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
"General Bot" is a registered trademark of Pragmatismo.io.
The licensing of the program under the AGPLv3 does not imply a
trademark license. Therefore any rights, title and interest in
our trademarks remain entirely with us.