| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
passes the basic smoke test, nothing else done (doing this to distract
myself & since people expressed interest in maybe trying to run an
instance again).
|
| |
|
|
| |
otherwise it just fails to start with an error
|
| |
|
|
|
|
|
|
|
|
| |
this allows setting options via an environment file that is passed to
the systemd units, in addition to the ones set during build time of the
package.
For now this is tailored to SECRET_KEY, but it may be useful for other
settings as well (e.g. EMAIL_HOST_PASSWORD), and I'm not sure if it
takes priority over the build-time settings ...
|
| |
|
|
|
|
|
|
| |
this should be mostly usable for actual deployments. Only thing that's
really still annoying is having to set the SECRET_KEY via Nix, since
not having set it makes the package fail to build. But it doesn't
actually end up in the derivation, so changing it afterwards should be
fine; I've just not tested that yet.
|
| | |
|
|
|
this is still missing:
- a nice way to do settings
- lots of testing (run the manage.py test script in a nixos test?)
- an actual way to deploy this in a halfway reasonable way
|
