-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release: 6.0.1 #568
Release: 6.0.1 #568
Conversation
Note the docker-compose-mysql.yml needs to be updated to MySQL 8. Picking the bookworm image to match the debian version used in Dockerfile.
|
One thing that was mentioned in their release news that I think needs special testing is they mentioned moving the assets and themes stuff around. We need to double check that we install any assets or themes in the correct place. https://www.redmine.org/news/147
Ofcourse now that 6.0.1 has been released. I'd recommend we skip to that version as well. |
03fcf21
to
e72bdad
Compare
e72bdad
to
ad2489e
Compare
ad2489e
to
f5d8b34
Compare
Hi @jcormier, Thank you for your prompt feedback. I've updated the commits to reference version 6.0.1 directly, skipping over 6.0.0. I also adjusted the MySQL configuration as per your instructions. Here’s the updated YAML: services:
mysql:
image: mysql:8.0-bookworm
environment:
- MYSQL_USER=redmine
- MYSQL_PASS=password
- MYSQL_DATABASE=redmine_production
- MYSQL_RANDOM_ROOT_PASSWORD=yes
volumes:
- /srv/docker/redmine/mysql:/var/lib/mysql
# https://www.redmine.org/projects/redmine/wiki/MySQL_configuration
command: --transaction-isolation=READ-COMMITTED I retained the - - MYSQL_CHARSET=utf8mb4
- - MYSQL_COLLATION=utf8mb4_unicode_ci Are these two parameters no longer necessary? Regarding the asset migration, I'm not entirely comfortable proceeding on my own. After reviewing the code, I noticed the If this is something you could handle quickly, given your familiarity with the code, it might be the more efficient approach. That said, if you’d prefer to guide me through it, I'm more than willing to give it a try, though please bear in mind I'm not yet at a senior level in Docker. Thank you again! |
Thanks I overlooked that. I thought that was resolved in 8.x but not according to the redmine docs so good call.
They are now the defaults for MySQL 8.x. Thanks for checking.
Let me take a look. Its probably a single path change in the functions file. Thanks for the quick follow up. |
Looks like the only change needed is
|
The MySQL is still buggy. Sorry for not noticing before. I sent one more commit (to be squashed later before merging). @@ -3,7 +3,7 @@ services:
image: mysql:8.0-bookworm
environment:
- MYSQL_USER=redmine
- - MYSQL_PASS=password
+ - MYSQL_PASSWORD=password
- MYSQL_DATABASE=redmine_production
- MYSQL_RANDOM_ROOT_PASSWORD=yes
volumes: |
Nice. Let me see if I can understand what is going on behind the scenes. |
The /srv/docker/redmine/redmine folder get volume mounted into the docker container at /home/redmine/data
Yes, it's the location where the redmine tarball was extracted "installed". Tends to be /home/redmine/redmine in the docker container.
Yeah. |
Nice. PS: Feel free to rebase, reorder, squash, do anything with my commits. |
No rush. If you can squash the MySQL pass fix and add the themes commit. I think this should be mergeable. |
Signed-off-by: Abinoam Praxedes Marques Jr. <[email protected]>
c6af787
to
4460201
Compare
I noticed a message on mysql configuration.
As per https://stackoverflow.com/questions/55559386/how-to-fix-mbind-operation-not-permitted-in-mysql-error-log it is related to the MySQL 8.x on. I added a commit with the instructed fix (I checked and it made the message disappear).
|
It's working. I guess the problem with the info page was related to my browser's session problem. |
Let me know if you spot anything more to fix before merging. Otherwise, feel free to do it! |
Thanks @abinoam. I created a 5.1-stable branch and have merged your changes into master. |
Congratulations @jcormier and the whole team of contributors for maintaining this repo.
I'm really impressed how well documented is the process of crafting a new release.
It was really easy and straightforward.
I have run the tests and the instance worked perfectly. Screenshot attached.
The only caveat was that the
test-relase
expects a directory calledcerts
with the openssl thing inside it.I have updated Makefile to do the this automatically (based on the instructions provided by README)