ceres/mux.go, branch step-re-orderingRecipe server for your favorite disheshttps://cgit.xengineering.eu/ceres/atom/mux.go?h=step-re-ordering2023-04-28T08:44:29ZIntroduce routing table2023-04-28T08:44:29Zxengineeringme@xengineering.eu2023-04-25T15:39:48Zurn:sha1:f456fa1a6d3a6633af3b420f1eddbc1a96ffcdf1
This removes a lot of repetative code.
Implement recipe deletion2023-04-01T16:21:27Zxengineeringme@xengineering.eu2023-04-01T14:03:49Zurn:sha1:88107366bce6b7f7c788171a18c40ad102904ff4Reduce to ID and Markdown2023-03-31T19:46:53Zxengineeringme@xengineering.eu2023-03-31T18:41:48Zurn:sha1:39298f14d366b351708e7f5ef30d1b6575155792
The upstream URL can be encoded easily by the user in the Markdown-based
description. The title can be parsed by the first found top-level
heading in the Markdown text.
Thus these two columns are no longer used. To avoid an additional
migration they will be kept in the database.
Remove image functionality2023-03-31T17:47:55Zxengineeringme@xengineering.eu2023-03-31T17:47:55Zurn:sha1:f1308a436040f3a72e058e10ec2693cfb599da30
Recipe images are currently complicated to implement and have little
use. Probably they will not be covered in the next release.
Apply go fmt *.go2023-02-11T17:19:30Zxengineeringme@xengineering.eu2023-02-11T17:19:30Zurn:sha1:ced1e404bd762abb114321334a3812805dee7059
This auto-applies the recommended Go codestyle.
Make multiplexer regular handlers2023-02-11T12:51:21Zxengineeringme@xengineering.eu2023-02-11T12:51:21Zurn:sha1:06a09ecebb3e7631044963e374671edf15d61213
Multiplexer functions used to return closures which are able to handle
HTTP requests for historc reasons. Now the multiplexers can be regular
HTTP handlers which is simpler.
Switch to global database pointer2023-02-11T12:46:45Zxengineeringme@xengineering.eu2023-02-11T12:46:45Zurn:sha1:6b52b4bbc81c64b29daff043b83e21c38f332052
Passing the database pointer around is a lot of text and has no benefit.
Switch webserver to global config struct2023-02-11T12:02:41Zxengineeringme@xengineering.eu2023-02-11T12:02:41Zurn:sha1:7e517ada827abc2658bb07347bc656c10860e091Migrate to multiplexer concept2023-02-09T20:51:48Zxengineeringme@xengineering.eu2023-02-09T19:52:36Zurn:sha1:4f0c5b2e5eb1277e6b5a6ba347ce08fd34cf1326
This introduces a layered approach to handling HTTP requests:
- server layer
- path layer
- request layer
The multiplexer file cares about the path layer. It delegates the
request handling to handlers from the request layer.