Remove complete implementation

2023-09-17T09:07:08Z

Restarting from scratch seems to be the fastest approach to switch to sqlite and get rid of some other structural mistakes from the past.

Fix add_recipes with default JSON

2023-04-28T08:44:29Z

Introduce routing table

2023-04-28T08:44:29Z

This removes a lot of repetative code.

Verify JSON input

2023-04-28T08:44:19Z

Without verification the text input is simply saved to the file. This is no problem for the recipe editing but since the json.Unmarshal functino will also fail on the index and recipe page this recipe will simply disappear from the web server while the file still exists on disk.

Replace JavaScript on edit page by form

2023-04-23T20:01:50Z

This is actually possible when using

instead of <pre>. With
this change the recipe server has full support for browsers without
JavaScript.
</article>
<article>
<h1>Update edit page</h1>
<p>2023-04-22T18:28:54Z</p>

</article>
<article>
<h1>Remove legacy Recipe struct</h1>
<p>2023-04-22T17:28:54Z</p>

</article>
<article>
<h1>Implement index page with JSON</h1>
<p>2023-04-22T17:17:04Z</p>

</article>
<article>
<h1>Implement basic recipe target with JSON</h1>
<p>2023-04-22T15:54:57Z</p>

</article>
<article>
<h1>Allow empty recipe list</h1>
<p>2023-04-13T18:21:58Z</p>
This is useful for the case that no recipes exist or the recipe data
folder does not exist.
</article>
<article>
<h1>Apply go fmt</h1>
<p>2023-04-13T16:52:12Z</p>

</article>
<article>
<h1>Do not hardcode data directory</h1>
<p>2023-04-13T15:59:37Z</p>

</article>
<article>
<h1>Switch to unnested config</h1>
<p>2023-04-12T16:50:34Z</p>
This is now just not needed.
</article>
<article>
<h1>Implement markup to HTML conversion</h1>
<p>2023-04-12T16:40:53Z</p>
The new custom and text/gemini inspired markup has to be converted to
HTML to display the recipe.
</article>
<article>
<h1>Move title parsing to new markup.go file</h1>
<p>2023-04-08T20:15:45Z</p>
The new recipe markup which replaces Markdown will need an own file to
be implemented.
</article>
<article>
<h1>Remove Markdown rendering</h1>
<p>2023-04-08T20:15:45Z</p>
This step prepares moving to a new, custom and easily parsable markup
language.
</article>
<article>
<h1>Switch from MariaDB to files</h1>
<p>2023-04-02T19:52:10Z</p>
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.
</article>
<article>
<h1>Improve user interface</h1>
<p>2023-04-01T16:37:47Z</p>

</article>
<article>
<h1>Implement recipe deletion</h1>
<p>2023-04-01T16:21:27Z</p>

</article>
<article>
<h1>Reduce to ID and Markdown</h1>
<p>2023-03-31T19:46:53Z</p>
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.
</article>
<article>
<h1>Remove image functionality</h1>
<p>2023-03-31T17:47:55Z</p>
Recipe images are currently complicated to implement and have little
use. Probably they will not be covered in the next release.
</article>
<article>
<h1>Make add.html a template</h1>
<p>2023-02-12T18:46:48Z</p>
This allows to use partial HTML files via Go's templating features.
</article>
<article>
<h1>Centralize templating</h1>
<p>2023-02-12T18:18:48Z</p>
This makes templating easier and allows to use partial templates.
</article>
<article>
<h1>Remove most function-inline comments</h1>
<p>2023-02-11T17:31:50Z</p>
Docstrings for functions are a good thing. But the inside of a function
should be written in a way that is self-explaining. Thus inline comments
are just extra stuff to maintain and read.
</article>
<article>
<h1>Apply go fmt *.go</h1>
<p>2023-02-11T17:19:30Z</p>
This auto-applies the recommended Go codestyle.
</article>
<article>
<h1>Rework logging</h1>
<p>2023-02-11T17:06:52Z</p>
Logging during a request is at the moment not really needed. Printing
the config to the log was a stupid idea too.
</article>
<article>
<h1>Switch to global database pointer</h1>
<p>2023-02-11T12:46:45Z</p>
Passing the database pointer around is a lot of text and has no benefit.
</article>
<article>
<h1>Migrate storage.go to global config</h1>
<p>2023-02-11T12:08:04Z</p>

</article>
<article>
<h1>Switch webserver to global config struct</h1>
<p>2023-02-11T12:02:41Z</p>

</article>
<article>
<h1>Remove commented code</h1>
<p>2023-02-09T21:00:32Z</p>

</article>
</main></body></html>

ceres/handler.go, branch step-re-ordering

Remove complete implementation

Fix add_recipes with default JSON

Introduce routing table

Verify JSON input

Replace JavaScript on edit page by form