For a project I’m working on, I’m quite hackily using the Caddy config as a sort of database to hold part of the state of my app. Trying to avoid a real backend as long as possible while prototyping. I’m curious if there’s any way to store generic data this way without Caddy choking on the config, since it’s gotten to the point where I’m doing a lot of processing to interpret the config.
That’s pretty vague. It entirely depends how you mean to use that “data”.
But there’s the map and vars directives. See the docs.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.