Docs
Running a site
This section is for the people who deploy and look after Gansey sites, whether a studio hosts them or a client runs their own. It covers what a deployment is made of, how configuration is read, how updates, licences and backups work, where the logs and health checks are, how pages are cached, the security settings worth knowing, and every command the gansey binary takes.
Every site is one gansey executable, one Postgres database and one folder of files. Most day-to-day work happens in the admin; the command line is there for setting a site up, scripting it, and recovering it when the admin is out of reach.
In this section
DeployingA Gansey deployment is four things:ConfigurationSettings are read in layers, each overriding the one before:Updates and licencesA site updates itself from a hub: another Gansey site that publishes core releases and answers licence checks.BackupsA backup is a folder under [backups].dir named after the time it was taken in UTC, such as data/backups/20261016-030000/, holding:Logs and healthGansey always logs readable lines to the console.Caching and performancePublic pages change only when something is published, so Gansey keeps each rendered page in memory, by path (and by language prefix, when a module serves the site under prefixes).SecuritySigning in creates a session: a random token sent to the browser in a cookie, of which only the SHA-256 hash is stored.Command lineEvery command is a subcommand of gansey.