contentdb
contentdb copied to clipboard
Addition of a link to release notes
Problem
I think a link to release notes would be a useful and informative addition. Similar to the website, repo, issue tracker and forums' links.
Solutions
Add a new field to the web form, database, cdb.json parser, and I would recommend displaying a "Changelog" link between "Source" and "Forums", and maybe also next to the "Versions" section.
Alternatives
Not adding a link?
Additional context
None.
Hi, can I give this a shot?
@Manish-Giri Hi, can I give this a shot?
Sure!
Take a look at how "website" is implemented for a guide.
You'll need to:
- Add a field to the Package table / model
- Create a migration
- Add a field to the PackageForm
- Use that field in logic / package
- Show it on templates / packages / view
- Add to api (done in get dictionary in the package model)
@rubenwardy Thank you for sharing these steps, I'll get started on it!
@rubenwardy I noticed some issues while running the steps in the Getting Started doc.
The containers that get created after running docker-compose are all named using -, while the shell scripts in utils seem to look for containers that are named using _. Here are some screenshots -
-
Here are some of the running containers after running
docker-compose up --build. Notice the name -contentdb-app-1- -
The
run_migration.shscript looks for a container calledcontentdb_app_1, which doesn't exist and so the command fails - -
If I manually rename the name in
run_migration.sh, same behavior is seen in the next step, inbash.sh-
- If I make these manual modifications, things seem to be working -
I think it's failing in Step 2 now
Yeah, if you're using a newer version of docker-compose you need to use - and not _
Note, as of https://github.com/minetest/contentdb/commit/4ef3aae193ddf5f2564c87a1ddb0d79037d784b9 the - vs _ issue is fixed
Thank you, I'll get back on this
Just wanted to say thank you @Manish-Giri and @rubenwardy ! The new release notes panel looks great!