Running your own server

What a Joripo server is made of, running one on a Windows computer, where the data lives, the database, keys, backups, and reaching it from the field.

An organisation can run Joripo on its own infrastructure (the Enterprise plan). These pages are for whoever runs that server. Parts of the self-hosting path are still being finalised; those pages say so under their title, and describe what works today.

What a Joripo server is made ofThe engine, the file store that is the record, the database that indexes it, and the choices for where to run them.
A server on a Windows computerRunning Joripo on a Windows desktop or laptop: what it needs, starting it, the first owner, and what to switch on in Windows. Being finalised
The storage rootWhere Joripo keeps its files, how they are laid out, why names never move data, moving to another drive, and what never to do.
The databasePostgreSQL as the index over the files, what only the database holds, upgrades that stop the server rather than run half-done, and rebuilding the index.
Keys and secretsThe secret key, the data key for encryption at rest, the maintainers' credentials, and what changing each one does.
Backups and restoreThe verified backups the server makes of its files, keeping a copy off the machine, backing up the database, and restoring step by step.
Reaching the server from the fieldGiving phones in the field an https address: a quick tunnel, a permanent address of your own, plain http on the office Wi-Fi, and an address per organisation. Being finalised