The first thing to do should be connecting the environment to your git repo. For this you will need a GitHub account, so please create one if needed.
Now we can connect this Mindsmiths environment with the Github account you have or you just created. To do that follow these steps this:
- Open terminal and run this command to create the SSH key and just press ENTER on all of the questions:
ssh-keygen -t ed25519 -C "your_email@example.com"
(change your_email@example.com with your email) - Run
cat /root/.ssh/*.pub
and copy the output of the command - public part of your SSH key (don't worry public part of the SSH key can be seen by everyone, it's not a secret!) - Go to this link (takes you to the Github's page for adding new SSH key) and paste the public key you copied under the "Key" part
- You can set the "Title" to whatever, it's just for you to know where it's from - we recommend something like "username-mindsmiths-free" (e.g. hrco-mindsmiths-free)
Now it is time to push the code to the connected repo, do this:
- Create a new repo following instructions on this link
- Run this command in terminal of your Mindsmiths environment:
git init
- Set the name and email the git will know you for with commands (change values for "you@example.com" and "Your Name"):
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
- Add the remote with:
git remote add origin git@github.com:<github_username>/<github_repo_name>
- Now run these commands to push all the files to the repo:
git add .
git commit -m "First commit: pushed all the Mindsmiths initial repo files"
git push --set-upstream origin master (answer "yes")
(It will take some time because of the big size of the files)
That's it you have your Github account connected
To help you get started with the platform, you can check out the tutorials and supporting documentation
If you need technical (and emotional) support, you can always reach out to us in our Discord channel
For frequent issues, there is a short rundown below.
The main directories are the following:
- config: directory containing all the configuration files
- models: symlink to the directory containing the agent models
- rules: symlink to the directory divided into subdirectories with the names of the agents you define. The rules referring to each agent are inside the respective subdirectories (e.g. rules/smith/Heartbeat.drl).
- services: directory containing all services you add to the platform. In the initial phase contains only the rule engine service.
Once you are satisfied with your product, and you would like to deploy it to production, just reach out. We'll take you through a simple process and help you set up the production environment.
Error: Cannot access target/app.jar file. Solution: Remove the folder in path services/rule_engine/target and run again.