| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
The default ExecStart implementation in the module, escapes all stings.
This does not work for us because we need to use the `$CREDENTIALS_DIR`
environment variable, for the credentials deployed in den
`LoadCredential` option
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
| |
This user is intended to be used for remote-builds
|
| | |
|
| |
|
|
|
|
|
| |
The unit had the potential to fail, if the build took longer than the
default timeout. This is obviously not ideal, so the timeout was
removed, as all nix builds should be safe enough not to devour
resources.
|
| |
|
|
|
|
|
|
| |
As the nix-sync service should _never_ commit new stuff, this rebase
should always be a fast-forward, i.e. it works without manual
intervention.
Without the rebase as argument, this services would break, when the
history gets rewritten, for example on a amended commit.
|
| |
|
|
|
|
|
| |
The timer before hand started `repo.interval` after it self was started,
i.e., it was a oneshot timer. This change now fixes this by make the
point the timer activates relative to the time elapsed, since the
associated unit was last started.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| |/ |
|
| | |
|
| |
|
|
| |
age secret
|
| | |
|
| |
|
|
| |
users
|
| | |
|
| | |
|
| |\ |
|
