It is broken and it has been like that for a couple of months so we'll
just disable it completely. I mostly use the web UI with manual
management of archiving anyways.
Apparently, it doesn't really log the errors in the journal so it can
make the service failed for no reason. It can be configured to redirect
it to journal.
This is to easily install launcher plugins and scripts in NixOS. I don't
know if this is also possible on home-manager (which I think it could be
since it also has the capability to set files).
I didn't realize `network.target` is very ambiguous. The next best thing
for booting up the service after the system is up is `default.target`
but we're being explicit here for NixOS services just to make sure.
There is the `--paths` option for that purpose. It also eliminates the
workaround for creating the directory before starting the service for
newly-bootstrapped systems.
The several hardening options have also been corrected.
Structure-wise, it is pretty similar to the gallery-dl service. It was
about to be combined into a bigger service module as a dedicated service
for multimedia archiving but it is better to have them modularized in
the long run.
It can now add and schedule archiving tasks. Since archivebox will use
Crontab module (which uses `/usr/bin/crontab`), the scheduling with the
interface is out of the question. What better way to make it possible
than creating a home-manager module for it?
Now, the configuration is made into a proper Nix configuration with the
output being converted to INI format.
For mapping the types, look for `mopidy/config/types.py`. The only
quirky mapping so far is the list type.
It is just an adapted version from the NixOS module. I'll eventually
figure out how to be 'properly configured' with the Nix language through
the `lib.generator`.
While it is easier to maintain the modules by prefixing them all with
`modules`, it is not easy when used from other flakes and/or modules.
This is my attempt on making it easier with appropriate namespaces.
Update home-manager user from the restructure
Now the browser-related cleaners are separated from the default cleaner
lists and has to be activated with `withBrowserCleanup` option.
Browser caches cleanup are also added as part of the updated module.
