Re: split current-toplevel for guix compatibility

[Nala Ginrut]

Hi Mortimer!

Mortimer Cladwell writes:

> OK great! Where do we start?
>
> Do you want to create a dedicated guix branch or do I issue pull requests
> to an existing branch?

GitLab is restricting the committers and bandwidth of each
namespace. GNU Artanis is under HardenedLinux namespace now, So
I think it's better to create fork rather than commiter+branch model.

> I can test if temporary files moved to /tmp/myapp is compatible with a gnu
> make install. If it is, is there any need for the server.guix
> variable?

There're several situations requires mutable files:

1. (current-toplevel)/.route
This is a temporary file that will be genreated when it inexists. So
it's easy to fix.

2. db/migration
3. conf/artanis.conf
4. lib/
These paths are mutable, but if we treat a webapp as a package, people
may not need to modify them. The modified version should be a new
version webapp that can be upgraded.

> Another need for server.guix would be to determine the default location of
> artanis.conf which can't be in /gnu/store/.../myapp/conf with guix.  If
> ../myapp/conf is eliminated as an option i.e. only
> /etc/artanis/artanis.conf or use of the --config flag is enforced, then
> maybe a server.guix variable is not needed.  I use
> ~/.config/myapp/artanis.conf

I think the publisher of the webapp can confirm the config file, and the
end user may choose to load their prefered config with -c, of course,
the DB username and passwd can also be specified, which should be
emptied in conf/artanis.conf

--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
Fingerprint F53B 4C56 95B5 E4D5 6093 4324 8469 6772 846A 0058

signature.asc
Description: PGP signature