-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[bitnami/wordpress] Roots / Bedrock Integration #67123
Comments
Hi, Thank you so much for the feature request. The bitnami scripts tries to create environment variables in wordpress-env.sh for most of the locations. However, if using bedrock fully deviates the structure of the default wordpress installation I'm afraid that's something we cannot afford to officially support. About the $app value, this is a parameter of the |
Just for show'n'tell I've created a PR to demonstrate minimal modification to get wordpress + roots/bedrock and roots/sage working in bitnami container. I understand that this thread is going to be closed, but I wanted to leave some information for anyone else looking to build a similar solution. |
Thank you so much! The community will benefit from this |
I have successfully deployed
|
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
bitnami/wordpress:latest
What is the problem this feature will solve?
Hi!
It is extremely hard to go over every script in Bitnami's library and edit hardcoded WordPress values, only to end up with a failing build. Extending the image via the /docker-entrypoint-init.d volume is impossible due to the rootless nature of the image. The Bedrock framework only changes the folder structure of WordPress, yet I have been modifying scripts for two weeks now with no success.
Steps to install bedrock:
Besides.. how do you run this script to provide $app variable.
What is the feature you are proposing to solve the problem?
I PR as soon as I would get this working.
What alternatives have you considered?
not really
The text was updated successfully, but these errors were encountered: