Where Does cState Store Pages?
Where self hosted cState keeps pages in config on Linux servers. Full paths are listed below. More below.
Last updated
cState is status pages with file config. Your systems live in its config file. Pages render from that file on each visit.
Same config file means same status page anywhere cState runs. Exact file names are stable across late releases. Keep full backups before upgrading. For moves, copy the config file. Partial setups miss issue templates that pages depend on. When in doubt, verify paths inside the app before trusting a remembered folder. Screenshots of settings help when support asks for reproduction steps later.
Where CState Status stores this, by platform
/var/www/html/config (cState file, no database)
Pages live in the cState config file. Copy it for moves. No database exists to dump. Match releases before importing old formats.
Frequently asked questions
How do I migrate cState to a new server?
Back up the cState config file with services stopped, then install the same release on the new server before restore. Pages follow the config. Mixed releases can refuse old formats, so match versions first. Keep status texts separate from shared copies.
Does cState keep incident history?
No. cState renders pages from its config file without keeping incident history itself. The server holds the config plus theme cache. Reinstalls reset views but never touch an external log. Treat the config file itself as the backup.
Notice an outdated path? Let us know.