MovingBlocks/FacadeServer-frontend

Improved instructions / more solid front-end setup

Cervator opened this issue · 0 comments

So this repo originally lived on @gianluca-nitti's personal account before it was transferred to MovingBlocks. Prior to that it had a GitHub page working at https://gianluca-nitti.github.io/FacadeServer-frontend/ as well as the manual install on http://utility.terasology.org:8000 powered by a minimal Python web server.

The GitHub page did its thing as GitHub pages do, but now it seems to be running into our MovingBlocks org page's ancient config that involves a redirect to terasology.org, so https://movingblocks.github.io/FacadeServer-frontend doesn't actually work. Need to look at that and see if maybe we need to update the org page to a newer config approach where it won't bowl over project/repo pages.

The manual install was run somewhat more primitively, like so:

  • login with ssh to utility.terasology.org
  • cd in the ~/FacadeServer-frontend directory
  • run nohup python -m SimpleHTTPServer > nohup.out

That we should probably replace with a nice little nginx setup that will auto-start after reboots (whoops, current approach doesn't), and perhaps throwing in our utility.terasology.org LetsEncrypt cert.

While some of that may not matter to 3rd party users of this repo (if there are any) maybe we could provide some more good instructions on how to deal with all that while setting up more properly.

Somewhat related: MovingBlocks/FacadeServer#11