| Age | Commit message (Collapse) | Author |
|---|
|
The default use case should be to not inject example recipes.
|
|
This makes it easier to run unit tests.
|
|
This variable will be the only used representation for version
information. It can trivially be used for an equality check. Further
data as semantic versioning must be parsed from this string.
|
|
The output of `git describe --dirty --always` is passed as a string via
Go build flags.
|
|
Using a build system like Make allows to execute more complex builds
while the user interface is still simple. The Makefile added by this
commit is just a basic starting point.
|
|
Restarting from scratch seems to be the fastest approach to switch to
sqlite and get rid of some other structural mistakes from the past.
|
|
That way only the system user setup and ownership change has to be done
by the packager / installer.
|
|
There were some templates missing.
|
|
|
|
Using a database is way more complex (see the commit statistics of this
commit) than using files to store recipe data. Also administration and
usage is simpler.
|
|
This project is not so big that it needs multiple packages.
|
|
This makes it easier to maintain and it looks better.
|
|
This was based on recommendations from the Arch Linux wiki. Because they
could maybe break something on other distributions they are removed here
and maybe re-introduced later in a packaging repository.
Furthermore the Makefile is more readable this way.
|
|
This drops also the -d flag and the database/user config option.
The -d flag used to override specific parts of the config file. This is
just confusing behaviour. Instead a new config/debug.json file is
introduced with useful default values.
Instead of configuring the database user via the database/user entry in
the config file, the user is determined from the Linux user of the
server process. This enforces that a database user with the same name as
the Linux user is configured which is already described in the README.
|
|
This repository is just about the generic source code. Adapting it to a
certain Linux distribution which might be systemd based is up to a
packaging repository.
|
|
|
