I’m also working on a Debian package for Known (http://withknown.com/), i.e. apt-get install known.
I now also have an experimental FreedomBox image (only for CubieTruck right now) that has both node-restore and known, as well as subdomain and PageKite registration during install: http://debian-dev.freedombox.at/images/
This is a bit experimental, but I’ll try to improve it and also contribute this to the “mainline” FreedomBox code.
I guess maybe I could try creating a sockethub package as well.
Better late than never I think Anyway, if anyone tries any of this, please let me know…
a debian init.d script that calls server.js and starts restore on port 8020
a node-restore.conf Apache configuration file with proxy settings to forward requests to port 8020
So in theory after you install it, restore should already be running and be reachable through Apache without more configuration.
I’m not sure if this is how you typically “do” Debian packages. Should the package just get restore running and not configure the webserver? Or should the package also automatically configure the webserver as I have done it now.
Cool! For adding reStore to IndieHosters it doesn’t really matter if it’s an npm package or a Debian package. But for freedombox (which is a Debian thing) this is super important!