You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Name and Version
redmine:5.1.2
What is the problem this feature will solve?
Allow HTTPS access without re-building the container image
What is the feature you are proposing to solve the problem?
Make it easy to run a container and point to certificates and key for HTTPS.
In the past we have used binary packages for Redmine but these are gone in favour of containers and VMs.
Looking at https://github.com/bitnami/containers/tree/main/bitnami/redmine#how-to-use-this-image the only mention of SSL is for SMTP.
What alternatives have you considered?
Various people have workarounds but these don't co-exist with the idea of containers which should just work.
The text was updated successfully, but these errors were encountered: