ceres/README.md, branch step-re-orderingRecipe server for your favorite disheshttps://cgit.xengineering.eu/ceres/atom/README.md?h=step-re-ordering2026-08-11T09:22:48ZIntroduce Dart infrastructure for frontend2026-08-11T09:22:48Zxengineeringme@xengineering.eu2026-08-11T09:14:54Zurn:sha1:40b3272f5660517a4c97f97afcc9c3ed787465a4
The Dart programming language is excellent for frontend use. It is
suitable to write command line programs, web interfaces with the builtin
JavaScript transpiler and cross-platform applications with Flutter.
To focus on a small number of languages Dart should now be used for
frontend purposes as Go is used for backend purposes.
Thus it is a valid option to start the migration for Ceres from Go +
JavaScript to Go + Dart.
This commit sets up the infrastructure. A `view/dart/ceres.dart` file is
added together with tooling to transpile to JavaScript, embed it into
the Go executable and serve it. Furthermore the script which just prints
a message to the console is added to every page.
Further commits can move existing code to Dart or add new code in Dart.
Explain package structure in README.md2024-10-23T16:17:44Zxengineeringme@xengineering.eu2024-10-23T16:17:44Zurn:sha1:e8f52156bf07a7668fb434eadb0e22f3e7dad648Remove Makefile and update README.md accordingly2024-10-23T15:56:35Zxengineeringme@xengineering.eu2024-10-23T15:56:35Zurn:sha1:649684b3b735f50ea33241286d231f977b8d0a89
This drops the build dependency GNU Make. The resulting build steps are
typical for Go repositories and thus more familiar for Go developers.
Fix build instructions2024-05-04T16:52:45Zxengineeringme@xengineering.eu2024-05-04T16:52:45Zurn:sha1:4c528668cc5d77c0859bdc237cef2e7c40b9b9d8
The missing submodule init / update caused build issues because the
external simple.css file could not be included.
Add usage instructions to README.md2024-05-01T14:23:53Zxengineeringme@xengineering.eu2024-05-01T14:23:53Zurn:sha1:1d6a23f6307ea1a1225ca8b2f2b91f78d1323416Add configuration file to semver API2024-05-01T14:17:01Zxengineeringme@xengineering.eu2024-05-01T14:17:01Zurn:sha1:ca4928a549251ad84c0ba2ef4179fa2174bbaabc
This aspect of Ceres is also part of the public API. A breaking change
in the configuration file format will require a version change which
indicates that.
Add build instructions to README.md2024-05-01T14:16:08Zxengineeringme@xengineering.eu2024-05-01T14:14:04Zurn:sha1:ae0cbafb0202355973572e208c75591d12c2250cDefine public API in README.md2024-05-01T09:36:09Zxengineeringme@xengineering.eu2024-05-01T09:36:09Zurn:sha1:ab6d2d7e2560761c9a369e623ddfbe0202188934
This is required according to semver.org.
Remove complete implementation2023-09-17T09:07:08Zxengineeringme@xengineering.eu2023-09-17T09:07:08Zurn: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.
Remove link to Gemini specification2023-05-01T17:24:04Zxengineeringme@xengineering.eu2023-05-01T17:24:04Zurn:sha1:20b251b70c475e718508c9ac7c5258d9a9e4ae29
This project does not use the Gemini markup anymore. It was replaced by
JSON.
Automate /var/lib/ceres creation2023-04-13T18:21:58Zxengineeringme@xengineering.eu2023-04-13T18:16:19Zurn:sha1:d82eae7034e0de30b5d61294cdb78c3ad8c1bbda
That way only the system user setup and ownership change has to be done
by the packager / installer.
Document creation of /var/lib/ceres2023-04-13T18:21:58Zxengineeringme@xengineering.eu2023-04-13T17:55:34Zurn:sha1:4ed4b195e9e78d22f9eae0925403de645b5bc30a
This is up to the packager. Inside that data directory the application
is allowed to create folders on its own.
Add link to gemini specification2023-04-08T20:34:38Zxengineeringme@xengineering.eu2023-04-08T20:34:38Zurn:sha1:a7a7bc184eb010166c8eb4a3255aad73b6d06edc
The gemini protocol specification includes a section about the
text/gemini MIME type. This file format is a easy to parse markup
language which should be used for the Ceres recipe server.
Switch from MariaDB to files2023-04-02T19:52:10Zxengineeringme@xengineering.eu2023-04-01T19:18:29Zurn: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.
Document expected environment and dependencies2022-11-11T19:23:31Zxengineeringme@xengineering.eu2022-11-11T19:23:31Zurn:sha1:a17ee3f500326ae7deec1c0a5067e3321ff5b9a1Document packaging and installation in README2022-11-11T19:11:04Zxengineeringme@xengineering.eu2022-11-11T19:11:04Zurn:sha1:23311fe01119fea5403f77e67372603f59eb1937Add documenatation for building and running2022-11-11T18:44:29Zxengineeringme@xengineering.eu2022-11-11T18:44:29Zurn:sha1:552a0a91f5b8450441e5160e50cca80e368525f4Remove user setup from initial migration2022-11-11T15:40:32Zxengineeringme@xengineering.eu2022-11-11T15:40:32Zurn:sha1:53d17214e4e9e1e630d625a51d05484c3770fad1
The initial migration used to add the Ceres database and user. This
works well for the production use case but is not that suitable for the
development / debugging use case where the default user of the developer
should be used.
With this commit the generic user setup is explained in the README which
can be applied to the developers Linux user aswell as a system user for
the production use case.
Link project page and changelog in README2022-11-07T20:17:44Zxengineeringme@xengineering.eu2022-11-07T19:35:30Zurn:sha1:c2bf31697f1105ef842306dea7154ba41e91b1e8Add existing work2022-11-07T20:17:44Zxengineeringme@xengineering.eu2022-11-05T20:25:31Zurn:sha1:1d6b45bebea66391a2a535a3bb328a5732aaa75d