| Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
You can't live without one.
|
|
|
|
|
|
|
|
|
|
Considering that the db dump takes longer than an hour, an hourly
service start time could lead to multiple dumps happening concurrently.
This should reduce this risk
|
|
Including this dump should remove the risk of a backup with a corrupt
PostgreSQL database. Initial test showed that the backup takes
around 32 GB and runs in under 3 hours.
There is one big oversight not yet included in this commit:
All services running a SQLite database are not included in this dump and
thus can not be safely recovered.
At present these are:
- etebase-server (db.sqlite3)
- murmur (murmur.sqlite)
(This is list was generated with `sudo fd sqlite /srv/`)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This isn't strictly necessary as we define the default config
|
|
nixpkgs
|
|
|
|
|
|
This doesn't work as nginx doesn't have the right permissions.
|
|
|
|
|
|
|
|
|
|
|
|
This is done to comply with the naming scheme employed at `vhack.eu`.
|
|
Otherwise, etebase might use the ipv6 ip, whilst nginx uses the ipv4
version. This prevents this issue
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
