Updated config template and renamed it to zotserver-config.txt.template
Updated setup shell script and renamed it to zotserver-setup.sh
Updated README.md
Main changes in the config template
"hubzilla" replaced with "zotserver" whenr possible
zotserver_db_name and zotserver_db_user values left empty by default
Main changes in the setup script
Main goal was to be able to install more than one Zot hub/instance on the same server, most changes were made for that.
"hubzilla" also replaced with "zotserver" most of the time
git repo can now be cloned using a path other than /var/www/html
a basic working Apache vhost will be generated if path is not /var/www/html
if zotserver_db_name and zotserver_db_user are not set in the config file, script will use the repository name ("zap", "misty", "osada" or "hubzilla") and make sure that an already existing db will not be overwritten.
file naming of daily shell script and in cron jobs is made using clone folder name and repo name, i.e. if a zap repository is cloned in /var/www/social, daily shell script will be named "social-zap-daily.sh".
Setup shell script was succesfully tested a few times along the way on a VPS that already has a Zap and a Misty instances running (none of them was damaged in the process).
Some extra work is probably needed for the USB drive backups part (i.e. one folder per hub/instance), probably won't work "as is" with a multiple Zot hubs/instances server.
### Changes in a nutshell
* Updated config template and renamed it to zotserver-config.txt.template
* Updated setup shell script and renamed it to zotserver-setup.sh
* Updated README.md
### Main changes in the config template
* "hubzilla" replaced with "zotserver" whenr possible
* zotserver_db_name and zotserver_db_user values left empty by default
### Main changes in the setup script
Main goal was to be able to install more than one Zot hub/instance on the same server, most changes were made for that.
* "hubzilla" also replaced with "zotserver" most of the time
* git repo can now be cloned using a path other than /var/www/html
* a basic working Apache vhost will be generated if path is not /var/www/html
* if zotserver_db_name and zotserver_db_user are not set in the config file, script will use the repository name ("zap", "misty", "osada" or "hubzilla") and make sure that an already existing db will not be overwritten.
* file naming of daily shell script and in cron jobs is made using clone folder name and repo name, i.e. if a zap repository is cloned in /var/www/social, daily shell script will be named "social-zap-daily.sh".
-----
Setup shell script was succesfully tested a few times along the way on a VPS that already has a Zap and a Misty instances running (none of them was damaged in the process).
Some extra work is probably needed for the USB drive backups part (i.e. one folder per hub/instance), probably won't work "as is" with a multiple Zot hubs/instances server.
Changes in a nutshell
Main changes in the config template
Main changes in the setup script
Main goal was to be able to install more than one Zot hub/instance on the same server, most changes were made for that.
Setup shell script was succesfully tested a few times along the way on a VPS that already has a Zap and a Misty instances running (none of them was damaged in the process).
Some extra work is probably needed for the USB drive backups part (i.e. one folder per hub/instance), probably won't work "as is" with a multiple Zot hubs/instances server.
b5efcac31dinto dev 2 years agob5efcac31d.