Recipe server for your favorite dishes https://cgit.xengineering.eu/ceres/atom/view?h=step-re-ordering 2026-08-13T19:15:49Z 2026-08-13T19:15:49Z xengineering me@xengineering.eu 2026-08-13T18:53:24Z urn:sha1:60bdc926dd7235fd55930ebd5b30c2e346f8ca59 TODO: Not all the information is provided there. This commit provides an unstable JSON API for communication with an upcoming Dart frontend. Later it might be part of the public interface for integration into other services. For this step it has to be ensured the semantics are not changing a lot in the future which is currently out of scope. 2026-08-11T09:22:48Z xengineering me@xengineering.eu 2026-08-11T08:36:58Z urn:sha1:5f66b2fc93d84cedd605bbacbd602cec98efc358 TODO: Add `onclick` to add functionality These buttons allow the user to move recipes steps up and down. The commit covers only the user interface change. 2026-08-11T09:22:48Z xengineering me@xengineering.eu 2026-08-11T09:14:54Z urn: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. 2024-11-03T15:06:58Z xengineering me@xengineering.eu 2024-11-03T14:50:08Z urn:sha1:c1b976edd0c27fdc488da7ff4c1b7551df0323cd This marks favorite recipes with a `⭐` emoticon. The favorite flag value can be set on the recipe edit page. Favorite recipes are listed first on the recipe list view. Furthermore as a second priority the created time stamp is used in the recipe list so that more recent recipes are listed first. 2024-10-24T18:24:46Z xengineering me@xengineering.eu 2024-10-24T18:24:46Z urn:sha1:43ed47bf3d51e25d3195870241bbe6619c43e459 This makes the recipe page less pretty. Nevertheless the URL is more visible to the user which makes it more likely that errors in the URL are detected. This change is based on user feedback. Invalid URLs were added which led effectively to data loss. 2024-10-24T18:14:14Z xengineering me@xengineering.eu 2024-10-24T15:24:00Z urn:sha1:9422e8194245c9cdbfa09b38c20173964349e2a2 This makes it easier to write a shopping list for the required ingredients. 2024-10-23T18:34:57Z xengineering me@xengineering.eu 2024-10-23T18:34:57Z urn:sha1:e66691083a2455c29b50a2970c0aba1d6afca753 The used `func(http.ResponseWriter, *http.Request)` return values made the HTTP handler factory functions quite unreadable. Thus it is switched to the http.Handler type. 2024-10-22T19:53:30Z xengineering me@xengineering.eu 2024-10-22T19:17:47Z urn:sha1:dbc874e2b9f300bea7a18deda32e784afb0ab89a The reason for the introduction of this dependency was that it was easy to setup routes with HTTP method restrictions. Since Go 1.22 this feature is part of the standard library. Method restrictions are part of the patterns used to register routes [1]. [1]: https://pkg.go.dev/net/http#hdr-Patterns-ServeMux 2024-10-13T17:55:38Z xengineering me@xengineering.eu 2024-10-13T17:52:28Z urn:sha1:473052ed8f2c83052ed5b47a7f4cec68ac2621a6 Reducing global variables makes it easier to understand functions independently of the rest of the code. Adding the new model.DB type as a custom variant of the sql.DB type makes it possible to write methods for the database which makes the code way more readable. 2024-10-12T13:24:33Z xengineering me@xengineering.eu 2024-05-17T20:49:15Z urn:sha1:9d3a5fb85dc02e87fab879855c4c3bace5f753f2 Instead a database transaction has to be used. Each database interaction should be wrapped into a transaction to make sure any possible change (even side-effects) can be rolled back in case of errors. 2024-09-11T18:25:54Z xengineering me@xengineering.eu 2024-09-11T18:25:31Z urn:sha1:54029aac92f17ec87d3ef0bb73fcdac271b209c9 This applies default Go code style recommendations. 2024-05-17T15:14:35Z xengineering me@xengineering.eu 2024-05-17T15:06:55Z urn:sha1:0416f520cff9716792ac0f3ade5f71187d07ac2e The recipe edit page HTML template did not contain the two time stamps "Created" and "LastChanged" as hidden form values. Thus the information was not passed from the backend to the frontend. On a save the recipe without time stamp information was injected into the backend. This effectively deleted any time stamp information. This commit fixes that bug by including all fields of the model.Recipe struct inside the form of the recipe-edit.html template. 2024-05-17T15:14:29Z xengineering me@xengineering.eu 2024-05-17T13:51:45Z urn:sha1:c61e45a5a260d9804ebc4f54814edf1e1b471ac3 This accepts only real numbers with a minimum step of 0.001 as input for the amount field of a recipe ingredient. The browser has the chance to give the user direct feedback that a non-numeric string will not work. 2024-05-15T18:42:09Z xengineering me@xengineering.eu 2024-05-15T18:42:09Z urn:sha1:d14aece3295405b4377ea20aabd9c621aace4922 If the recipe has no ingredients at all the "Ingredient summary:" text used to be displayed. This is not useful and confusing. It is removed with this commit. 2024-05-15T17:39:17Z xengineering me@xengineering.eu 2024-05-15T17:39:17Z urn:sha1:34880a0194f66e2b1808b45abfb01497d4816aaf It does not make sense to add empty steps. 2024-05-15T17:37:05Z xengineering me@xengineering.eu 2024-05-15T17:37:05Z urn:sha1:29c8c305c52b97248e505cdfc6b86e96f57d0a53 It does make sense to add an ingredient only with a type and no amount or unit like 'salt'. But it does not make sense to add an ingredient without a type like '5' or '2 l'. 2024-05-15T17:33:11Z xengineering me@xengineering.eu 2024-05-15T17:33:11Z urn:sha1:45a0a10c070e3dba33be01d4de4d094fd7f7394a This is the latest available release. Updated to keep up to date and adopt fixes. 2024-05-15T17:27:05Z xengineering me@xengineering.eu 2024-05-15T17:27:05Z urn:sha1:b48f4514a44450da1ad5da68ce434c2b87e721d0 This used to be named 'Ingredients: which might be confusing since ingredients are defined per step and the list at the top of the recipe is just a summary. 2024-05-15T17:20:01Z xengineering me@xengineering.eu 2024-05-15T17:20:01Z urn:sha1:d8b40f0a0a2ac2bcb8b9b690166ae7594c067298 the first text input of that new element. This supports using Ceres without a mouse and only with tab-based navigation with a keyboard. 2024-05-14T18:43:41Z xengineering me@xengineering.eu 2024-05-14T18:14:42Z urn:sha1:a87128138bdb301ede64049ec5068e47abb5c839 2024-05-13T19:52:48Z xengineering me@xengineering.eu 2024-05-13T19:51:43Z urn:sha1:b5b72880a0b6e9f188b532c9b2ad360ff1dab2ea 2024-05-12T18:52:25Z xengineering me@xengineering.eu 2024-04-07T10:04:11Z urn:sha1:bf328dd38a28cf44cfa81c7f1dcd95936d2d0301 2024-05-12T18:52:25Z xengineering me@xengineering.eu 2024-04-07T09:56:20Z urn:sha1:01d97189d245300d65ca31d650dd868d1d1fc0d8 2024-05-12T18:38:24Z xengineering me@xengineering.eu 2024-05-12T18:38:24Z urn:sha1:fec2fea87615e6ee3a6e73f7f98e021eee1b7098 This makes the JS function way simpler and removes a duplication of the step HTML code. 2024-05-12T18:20:14Z xengineering me@xengineering.eu 2024-05-12T18:20:14Z urn:sha1:64ece1c4455ed6f8e8be5cb8f060f14b6131823f This allows to use it in two places: - template for loop for backend-generated steps - a HTML template tag for frontend- / JS-generated steps 2024-05-12T18:06:17Z xengineering me@xengineering.eu 2024-05-12T18:06:17Z urn:sha1:f2800e8289e9637bb3227a5f9622edabf6529b0f 2024-05-12T18:01:02Z xengineering me@xengineering.eu 2024-05-12T18:01:02Z urn:sha1:cfeff398f0ad7e4205dc26b66ca2b46ebca24606 This makes it impossible to move the whole JS functionality into the central ceres.js script. Moving that JS code there makes caching possible and bundles all JS-related code in one file. The overall goal is to get rid of as many JS code as possible. 2024-05-11T21:08:42Z xengineering me@xengineering.eu 2024-05-11T21:08:42Z urn:sha1:907bd7e63f4cf3cb01bc678e09fc5b8962afe750 2024-05-09T10:19:35Z xengineering me@xengineering.eu 2024-04-23T16:47:30Z urn:sha1:a2aa866e630c45e1db4fadbb20cb1a9d24384a79 2024-05-09T10:19:35Z xengineering me@xengineering.eu 2024-04-23T15:42:58Z urn:sha1:eb000e0cc514ebca753970ddb9135e09cb885d7a This takes up way less space in the code and the actual user view.