| Age | Commit message (Collapse) | Author |
|---|
|
This shows some more markup features / edge cases.
|
|
|
|
|
|
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.
|
|
This prepares the switch to a file-based store of recipe data replacing
MariaDB.
|
|
|
|
|
|
|
|
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.
|
|
Recipe images are currently complicated to implement and have little
use. Probably they will not be covered in the next release.
|
|
Since there are no good solutions to upload the file and markdown
description text via HTML forms the edit page will upload the changes
using embedded javascript.
The page is now complete apart from the necessary javascript code and
the backend handlers.
|
|
|
|
This allows to use partial HTML files via Go's templating features.
|
|
|
|
This reduces copies of the same HTML code.
|
|
Recipes should be completely editable and removable. Thus this edit page
was added.
|
|
This makes it easier to maintain and it looks better.
|
|
A not existing data/storage folder could break the program with the
debug.json config file used. The .gitkeep file which is introduced with
this commit ensures that the folder exists.
|
|
|
