ceres, branch step-re-ordering

WIP: view: dart: Detect page

2026-09-22T17:40:04Z

view: dart: Log `web.window.location`

2026-09-22T17:22:23Z

This makes it possible to distinguish the miscellaneous pages of the website.

view: dart: Prefer single quotation

2026-09-22T17:15:37Z

This is the recommended quoting in Dart.

view: dart: Add dependencies including `web`

2026-09-22T17:12:40Z

This allows to read / write elements of the webpage.

view: dart: dart2js.sh: Use `dart pub get`

2026-09-22T17:10:42Z

This command makes sure dependencies are pulled. This is required to access elements of the web page from Dart code.

view: dart: Update analysis_options.yaml

2026-09-22T17:09:56Z

This configures linting to support writing good Dart code.

view: dart: .gitignore: Add .dart_tool

2026-09-22T17:08:12Z

These are cached files of the dart tool which should not be committed.

Introduce Dart infrastructure for frontend

2026-08-15T17:56:51Z

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.

Add JSON-based API under `/api`

2026-08-15T17:56:51Z

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.

Add `-version` suffix to VERSION.txt

2024-11-03T16:45:07Z

This follows the process described in RELEASE.md to make sure the development versions are not mixed up with the released ones.

Set version to 0.5.0

2024-11-03T15:54:04Z

Update CHANGELOG.md for version 0.5.0

2024-11-03T15:54:04Z

Fix RELEASE.md

2024-11-03T15:54:04Z

The changelog should be changed before updating the version to make sure changing the version is the commit which is tagged. Furthermore there was a mistake that the suffix `-devel` should be removed after release. Instead it should be added.

Fix version string

2024-11-03T15:54:04Z

This contained an unwanted newline.

view: Implement favorite recipes

2024-11-03T15:06:58Z

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.

model: Implement favorite recipes

2024-11-03T15:05:55Z

This adds the ability to store a flag `is_favorite` inside the database. The corresponding SQL migration is part of this commit. Furthermore the Go code in the model package is adapted.

Add file extension to LICENSE

2024-11-03T14:45:46Z

This makes it easier for humans and software to detect that this is a plain text file.

view: Display URL content on recipe page

2024-10-24T18:24:46Z

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.

view: Order ingredient summary by ingredient name

2024-10-24T18:14:14Z

This makes it easier to write a shopping list for the required ingredients.

Rework error handling of model.DB.Transaction()

2024-10-24T15:01:24Z

The functions in the sub-packages model, view and controller should not log too much. Instead they should return errors which can be extended by fmt.Errorf(": %w", err).

Switch to http.Handler

2024-10-23T18:34:57Z

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.

tools: Add unit tests to check.sh

2024-10-23T16:43:02Z

Fix unit tests

2024-10-23T16:42:20Z

API changes were not adopted in the unit tests.

Explain package structure in README.md

2024-10-23T16:17:44Z

Apply go fmt

2024-10-23T16:02:06Z

Remove Makefile and update README.md accordingly

2024-10-23T15:56:35Z

This drops the build dependency GNU Make. The resulting build steps are typical for Go repositories and thus more familiar for Go developers.

Inject version with embed instead of build flags

2024-10-23T14:04:22Z

The build flags made the basic build and debug calls quite complex and bound this strictly to Git repositories which is a problem if the source code is passed around as tar archive. Embedding this via Go's embed package and a VERSION.txt file makes this way easier. A simple `go build` command is sufficient to build ceres. To make sure the version string is extended by a `-devel` marker and that this marker is removed before a release a RELEASE.md file was added as a checklist for releases.

Remove github.com/gorilla/mux dependency

2024-10-22T19:53:30Z

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

Use `-race` for debug runs

2024-10-22T18:26:04Z

This option for the go tool activates a race condition detector. It makes building the executable slower. Nevertheless it is worth it since it detects a lot of race conditions and race conditions should be avoided as much as possible.

Run go mod tidy

2024-10-21T19:43:11Z