Recipe server for your favorite dishes https://cgit.xengineering.eu/ceres/atom?h=0.4.0 2023-09-17T09:07:08Z 2023-09-17T09:07:08Z xengineering me@xengineering.eu 2023-09-17T09:07:08Z urn:sha1:ea54de7d32e6b576ccfb430e7e57811b7c4587fe Restarting from scratch seems to be the fastest approach to switch to sqlite and get rid of some other structural mistakes from the past. 2023-04-13T15:59:37Z xengineering me@xengineering.eu 2023-04-12T17:04:29Z urn:sha1:ec1936c20647ba405bd2cc457c16a02dfdf56216 2023-04-12T16:50:34Z xengineering me@xengineering.eu 2023-04-12T16:50:34Z urn:sha1:4eacd5f54074c6cd73eaef4178c56843ce742445 This is now just not needed. 2023-04-02T19:52:10Z xengineering me@xengineering.eu 2023-04-01T19:18:29Z urn:sha1:bae6e34c9119750b2cba2a2ce6d88e9f8c895900 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. 2023-03-31T17:47:55Z xengineering me@xengineering.eu 2023-03-31T17:47:55Z urn:sha1:f1308a436040f3a72e058e10ec2693cfb599da30 Recipe images are currently complicated to implement and have little use. Probably they will not be covered in the next release. 2022-11-11T18:19:25Z xengineering me@xengineering.eu 2022-11-11T18:19:25Z urn:sha1:bdefa29fb2395eec79564145186d9ad1ec45dff3 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. 2022-11-07T20:17:44Z xengineering me@xengineering.eu 2022-11-05T20:25:31Z urn:sha1:1d6b45bebea66391a2a535a3bb328a5732aaa75d