Duplicate wp-config.php Files for my WordPress in Elastic Beanstalk Environment
I recently deployed a WordPress application using AWS Elastic Beanstalk with Nginx as the web server. Upon inspecting the file system, I've noticed that there are two identical wp-config.php files located in /var/app/current/ and /var/www/html/. I'm seeking clarification on why this duplication exists and where I should make edits to the wp-config.php file. I'd like to understand the purpose of this setup and ensure I'm following best practices for configuration management in Elastic Beanstalk environments. Any insights or guidance would be greatly appreciated.
- Newest
- Most votes
- Most comments
Hello.
Basically, if you edit wp-config.php located in the document root of Nginx, the setting will be reflected in WordPress.
If you connect to EC2 and look at the Nginx configuration file, the document root should be listed.
I think it's better to upload a new file in EC2 of Elastic Beanstalk than to directly modify it.
I think you are probably uploading the zip when creating the environment, but it is an image that the work will also be done when updating.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-versions.html
Relevant content
- Accepted Answerasked 9 months ago
AWS OFFICIALUpdated 10 months ago- How do I customize my nginx configuration to modify the "client_max_body_size" in Elastic Beanstalk?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 18 days ago
Thank you Riku for letting me know that it is better to upload a new file than to directly modify it.