Updating

Cloudlog on your own server is updated by fetching the new files and then opening the site. Opening any page applies the database changes that came with those files. You do not run a separate database tool.

The install page for your system has the commands. On Linux that is a short script, cloudlog.sh, which pulls the files, puts the writable folders back to the right owner, and requests the login page so the database catches up. A line in cron can run that script every night.

After an update:

• Log in. A new warning on the home page is worth reading.
• Open Debug if something that used to save now fails. The usual casualty is a folder that is no longer writable.
• Country files and the SOTA, POTA, and WWFF lists do not need refreshing just because the program changed. Refresh them when the data has changed, from Maintenance and Country files.

A hosted Cloudlog at magicbug is updated for you.

If the top of the page shows a red Developer Mode badge after an update, the server is running in development. That is a switch in the server environment, CI_ENV. Production is the normal setting. The badge is a warning that more internal detail is being shown than you want on a logbook other people can open.