Updates, Backups & Cron

Keeping the site current is a one-click job, and it is designed to be safe.

Updates and backups

From Admin, Updates you apply a new version with one click. Before anything changes, the updater takes a full backup (files and database) and stores it, then applies the new files and runs any database migrations. Your config, uploads and content are preserved, so an update never overwrites your settings or your edits. You can download a backup at any time.

Restoring a backup

Restoring is not the same as updating, and the difference is worth understanding before you use it. A restore replaces your site with the copy inside that backup: every page, post, user and setting created since the backup was taken is removed. It does not merge anything.

Because of that, the site takes a safety copy of everything as it is right now before the restore begins, and tells you its filename afterwards, so a restore you did not mean to do can be undone by restoring that copy. If the safety copy cannot be taken for any reason, you are told plainly rather than left to find out later. The Restore button asks you to type the backup’s date, because a yes or no box is easy to dismiss without noticing how far back you are about to go.

Admin activity

The bottom of the Updates page lists recent admin activity: sign-ins, updates applied, restores and backups deleted, each with who did it, from which address and when. If something on your site changes and you are not sure whether it was you, another admin, or someone who should not have been there, this is where to look first.

Cron

A scheduled job runs the site's background work: AI blog posts, the daily horoscopes for all 12 signs, the newsletter digest, translations and backups. Set a cron job on your host to call the site's cron URL at least once an hour. If your host has no cron, a built-in fallback scheduler runs the same jobs on ordinary visitor traffic, so the site keeps working either way.