Looking after Cloudlog¶
The cog at the top is the Admin menu. You only see it when your user is an administrator. Operators can log, and they cannot change the server.
Picture needed:
admin-menu.pngThe Admin menu dropped open: User Accounts, Global Options, Modes, Contests, Themes, Update Country Files, Maintenance, Plugin Manager, Debug Information.
The demo login¶
A new Cloudlog lets you in as m0abc with the password demo. That account is an administrator, and the password is the same on every fresh install.
Create yourself under User accounts, give yourself Administrator, log out, log in as yourself, and delete m0abc. Do this before anyone else can open the site.
The menu¶
- User Accounts. Who can log in, and whether they are an administrator. User accounts.
- Global Options. Switches for the whole site: email, registration, the public diary. Global options.
- Modes. Which modes the logging screen offers. Modes.
- Contests. Which contest names appear when you log a contest. Covered with Contest logging.
- Themes. Which colour schemes people can pick on their account. Themes.
- Update Country Files. The DXCC list. Country files.
- Maintenance. Contacts with no station, and the SOTA, POTA, WWFF, and LoTW lists. Maintenance.
- Plugin Manager. Extras someone has written for Cloudlog. Plugins.
- Debug Information. The page to copy when you ask for help. Debug information.
A copy of your own locations, logbooks, and contacts is Backup. In Cloudlog that button is under your callsign, next to the other copies of the log.
Keeping the program up to date¶
Updating is a job on the server: pull the latest files, and open the site once so the database catches up. The install page for your system has the commands, and a timed job that can do the file part every night. The short answers to the errors people hit after an update are on When something goes wrong.
After an update, log in and look around. The Debug page will show you if a folder has lost permission to be written to, which is the usual thing an update disturbs.