How deployments work
What a deployment is and how the platform chooses one.
One folder per site#
A deployment is a folder. It holds everything that belongs to one site:
| Folder | Holds |
|---|---|
data/ |
Configuration and structured lists, as JSON files |
content/ |
Pages, documentation and changelog entries, as Markdown files |
assets/ |
The theme file, images and icons |
Nothing in a deployment is code. The platform reads these files when the site starts.
These files are where a community's identity lives: its name, colors, artwork and words.
One site, one deployment#
A running Draconis site serves exactly one deployment. A setting named Deployment says which folder to use. Two sites are two copies of the same platform, each pointed at its own folder.
There is no switching between deployments while a site is running, and one site never shows another's content.
Changing a site#
To change a site, edit its files and publish it again. The site checks its files when it starts and refuses to run if something required is missing, naming the file and the problem.
Turning pages on#
Every optional page starts switched off. A deployment turns a page on in its configuration once the content for it is ready. While a page is off it returns "not found", and links to it are left out everywhere.