Score:0

Gitea under Configuration Management: Generated and Static Settings

in flag

I need to set up a Gitea server for an organization. The setup itself is easy, and I managed to bring up Gitea within an hour when installing it manually.

However, my organisation uses a configuration management tool, which handles secrets and configuration settings. So the idea is that I create /etc/gitea/app.ini using a configuration file template.

But when I run the Gitea setup, additional values are created, such as JWT tokens (JWT_SECRET in the [oauth2] section of the config file), which I clearly cannot make up before Gitea is up and running.

So on one side, I need to pre-define the app.ini, on the other hand, I need Gitea to control app.ini. But when my provisioning script runs, it will overwrite those settings.

Is it possible to split up those two sets of settings over multiple configuration file: one to pre-define statically, and one to be managed by Gitea?

Score:0
in flag

It turns out the JWT has only a "not valid before" date and therefore doesn't need updates. So it works fine with a single config file.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.