proposal : server re-organisation
Actually solidcommunity.net has been implemented :
- directly at
root. This makes things mixed with everything -- I propose to move the solid-server to/home/solid/solidkeeping data in /mnt -- A test-server will be created at/home/solid/test_solid-- utilities to manage the server, could be located at/home/solid - data are located at /mnt/volume_1on1_01/solid.community
-- I propose to replace this with
/mnt/volume_1on1_01/solidcommunity.net-- to locate the tes-server data to/mnt/volume_1on1_01/test_solidcommunity.net - I have no specific ideas to the data-backup expected for .db and data -- daily, weekly ... -- where, and how many (last, last and last-1, ...)
Before moving anything waiting for some comments, I just implement the test-server following the above lines.
- directly at
root. This makes things mixed with everything
Agree - the server should have its own operating environment rather than located in /root. As part of this, it should probably be a node global install if it isn't already. @jaxoncreed can confirm - and might be best to coordinate together on that.
- -- I propose to move the solid-server to
/home/solid/solidkeeping data in /mnt
Traditionally, /home is meant for an individual user account's home directory, so it wouldn't be much different than running out of /root. /var would probably be better. The pod data has to remain where it is because that is an external volume that's been attached and mounted. Config should be located in /etc, logs in /var/log.
- -- A test-server will be created at
/home/solid/test_solid
We should avoid running two instances on the same server. This can lead to unforseen consequences. We could provision a separate test server if necessary.
- I propose to replace this with
/mnt/volume_1on1_01/solidcommunity.net
Agree - though confirm with @jaxoncreed that there wasn't a reason he left this out of the original script for filename conversion. Will require the server configuration to be changed to point to the new location.
- I have no specific ideas to the data-backup expected for .db and data
Regular backups are already being done by Digital Ocean so we're covered there 👍