Updates to enable Eyesy web editor and improve install experience #2
Conversation
… files already committed.
…ick run/stop to include them.
…p of file paths and editor file display.
|
Thanks a lot for your work, this is amazing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
This aims to enable the webapp. It also aims to improve the install experience, so that new users should be able to run a single command to get all dependencies installed.
To test this (preferably with a clean Fates/Sidekick install):
The deploy script takes several minutes, as it is now installing all the Debian packages as well as Python and Node packages. Subsequent runs are much faster.
If everything went well, Eyesy should run, and the web editor should be available at http://norns.local:8080/
Changes:
** Debian python dependencies & nodejs
** Python packages psutil and cherrypy (necessary for the webapp)
** Node packages (necessary for the webapp)