aws-samples / aws-samples/eb-php-wordpress
wp-content symlink
- Dominant language
- PHP
- Stars
- 166
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I’m having hard time on adding persistence on all wp-content directory.
My main problem is that if I use symlink on wp-content, a lot of plugins/themes stop working because they use some __FILE__ and __DIR__ constants, and those constants return the real path of the file(the resolved path, so /wpfiles, where the EFS volume is mounted)
The result is all scripts/css have urls like : /wpfiles/themes/...
So I search for a way to mount directly the EFS on /var/app/current/wp-content, someone have some advices ?
Contributor guide
Research direction
Start by reading the repository's Elastic Beanstalk and EFS configuration instructions, focusing on wp-content and the /var/app/current/wp-content mount path. The issue does not name a configuration file or test; done would require a documented, supported approach for mounting EFS directly without symlink-resolved URLs breaking WordPress plugins and themes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, php, wordpress
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100