I installed Mistpark 2020 (a.k.a. "Misty") on the same VPS where my @!
Zap instance is running. As I'm rather lazy and not willing to type too many command lines to do so, I decided I'd use the homeinstall script provided
in the Misty repository (which is basically the same as in the Zap repository).
I knew that simply running the script "as is" would mess up my Zap instance, so I had to to a few things before letting the magic happen. In case anyone would be interested, here's what I did, step by step.
1. On the already installed Zap sideAs the
hubzilla-setup.sh script is designed for an installation in the /var/www/html/ folder for both Zap and Misty, I renamed the folder:
$ cd /var/www/
$ mv html zap
Then of course, I had to change the web server's configuration. I use nginx, so in my site's *.conf file I had to change
root /var/www/html/;to
root /var/www/zap/;In Apache, you'd have to change the DocumentRoot of your VirtualHost.
In order to have the Misty install script running safely, I also renamed the maintenance script from hubzilla-daily.sh to zap-daily.sh:
$ cd /var/www/
$ mv hubzilla-daily.sh zap-daily.sh
Then I edited zap-daily.sh and replaced every
/var/www/html occurence with
/var/www/zap. I did the same in /etc/crontab, where I also replaced
hubzilla-daily.sh with
zap-daily.sh and
hubzilla-daily.log with
zap-daily.log2. On the Misty sideAfter cloning Misty's repository in /var/www/html I made a few changes before running
hubzilla-setup.sh.
I replaced the following lines
elif git remote -v | grep -i "origin.*zap.*"
then
print_info "zap"
util/add_addon_repo https://codeberg.org/zot/zap-addons.git zaddons
with
elif git remote -v | grep -i "origin.*misty.*"
then
print_info "misty"
util/add_addon_repo https://codeberg.org/zot/misty-addons.git maddons
I'm not sure if "maddons" is the proper name to use, but it seems to work so far.
Here's another thing I should probably have changed on the setup script: replacing
function configure_cron_daily {
print_info "configuring cron..."
# every 10 min for poller.php
if [ -z "`grep 'Run.php' /etc/crontab`" ]
then
echo "*/10 * * * * www-data cd /var/www/html; php Zotlabs/Daemon/Run.php Cron >> /dev/null 2>&1" >> /etc/crontab
fi
with
function configure_cron_daily {
print_info "configuring cron..."
# every 10 min for poller.php
echo "*/10 * * * * www-data cd /var/www/html; php Zotlabs/Daemon/Run.php Cron >> /dev/null 2>&1" >> /etc/crontab
I didn't do it, so I had to add the line manually in /etc/crontab.
Finally, in
hubzilla-config.txt I changed the values in the following lines
# Database for hubzilla
hubzilla_db_name=hubzilla
hubzilla_db_user=hubzilla
After that I could run the install script safely. If I used Apache as my web server this would probably have been sufficient to have a Misty instance running smoothly besides my Zap instance. I actually had a few quirks related with letsencrypt (and probably the fact that athough it's installed Apache is disabled on my server) but I could handle them quite easily.
I must say, those install scripts provided with Hubzilla, Zap and Misty are really nice. They make the installing process really easy even for those who don't know much about running their own server.
