Comfort of a personal assistant for Linux systems. Currently features native google, yahoo, bing searches, weather conditions, videos from youtube and looking up for images as well, all in a very reliable structure and UI.
45
stars
45
forks
source link
Setup continuous deployment for jarvis as a permanent service #200
I am happy to announce that this PR sets up Jarvis as continuous deployment. This marks as first milestone in the production stage of Jarvis. With this:
The latest version of the master branch is automatically deployed at Heroku as the main backend. Users and developers can use this for testing and for managing end-users requirements for now. Later, we plan to make master as a branch for development main and production as a branch for end-users.
Builds and deployment would happen only when once the code is merged with master and the build in the Travis CI passes. we do not want broken code to go to the users.
This opens the much-required focus on the desktop app, the dashboard for Jarvis (planned) from where the matching statements would be designed and automated into the database of Jarvis.
With this getting merged, the concept of Jarvis is divided into two types: The static part and the machine-learned or dynamic part. The static part would be responsible for carrying out request and functioning of Jarvis like a normal conversation, etc. The dynamic part would be the machine-learned model, which would be used to add value t the normal requests sent to the backend. This value in requests would help perform a special type of queries that would be specific to the users.
I am happy to announce that this PR sets up Jarvis as continuous deployment. This marks as first milestone in the
productionstage of Jarvis. With this:The latest version of the master branch is automatically deployed at Heroku as the main backend. Users and developers can use this for testing and for managing end-users requirements for now. Later, we plan to make
masteras a branch for development main andproductionas a branch for end-users.Builds and deployment would happen only when once the code is merged with master and the build in the Travis CI passes. we do not want broken code to go to the users.
This opens the much-required focus on the desktop app, the dashboard for Jarvis (planned) from where the matching statements would be designed and automated into the database of Jarvis.
With this getting merged, the concept of Jarvis is divided into two types: The static part and the machine-learned or dynamic part. The static part would be responsible for carrying out request and functioning of Jarvis like a normal conversation, etc. The dynamic part would be the machine-learned model, which would be used to add value t the normal requests sent to the backend. This value in requests would help perform a special type of queries that would be specific to the users.