[PATCH] aurweb.spawn: Integrate FastAPI and nginx

Lukas Fleischer lfleischer at archlinux.org
Mon Jun 1 00:39:12 UTC 2020


On Sun, 31 May 2020 at 17:20:45, Frédéric Mangano-Tarumi wrote:
> > Even if the dev-only options are indicated by comments, I am not sure
> > whether it's a good idea to mix production and development configuration
> > like this. Can we put them in a separate file or at least a separate
> > section without too much effort?
> 
> aurweb.config is quite trivial so we could easily add mechanisms for
> handling environments or things like that. However, since these values
> are just ignored by production, I don\u2019t think it\u2019s a big deal.

> How about creating conf/config.dev with dev-specific options, and
> options most developers need to change (disable_http_login, etc.). In
> TESTING, we would change 3) to \u201cCopy conf/config.dev to conf/config\u201d.
> The downside is that when we add new required options to config.dev,
> developers need to update their conf/config manually.

With the current design, you already need to copy the config file to
/etc/aurweb/ on changes or use the AUR_CONFIG environment variable to
point to an alternative path (TESTING uses the latter). So maybe create
a development version of the config file as you suggested, add the
dev-only options only there and update the TESTING instructions to use
that file instead of the production config defaults?


More information about the aur-dev mailing list