You are viewing a single comment's thread from:
RE: Task Request: Jarvis - Heroku Implementation & Guide
I actually never really got into Heroku, but I think it would be quite neat for people to use a BaaS instead of hosting the script themselves on a server since Jarvis should run at least in the background round-the-clock.
The UI is in another task request. The idea is to have the following workflow in the end:
1.) Open UI
2.) Configure Jarvis
3.) Decide between running it locally, running it on a server or running it via Heroku
Now, many people would probably be overwhelmed, so a good step-by-step guide customized for Jarvis to get started with Heroku is important.
That clears it up, thanks!