Best way to install plugins persistently?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reading the repository's installation and deployment instructions, then inspect how the Elastic Beanstalk setup uses the EFS-backed shared assets described in the repository. The work is complete when a documented or implemented approach preserves installed plugins across instance reboots while retaining a practical update workflow.
Written by the indexing model from the issue text.
Description
Hello!
I'm a bit of a noob with both AWS and WordPress; I've been wrangling with the setup (routing to a custom domain, through HTTPS, etc.) for the last four days and finally have Vanilla WordPress setup and running as laid out in this guide--
BUT, I've noticed that whenever I install plugins through the admin panel they're wiped every time my EC2 instance reboots.
I'm assuming this is because the plugin source isn't bundled in with the deployment code and is only stored locally, so with every reboot it's gone forever and takes a reinstall. It appears though that plugin preferences are stored persistently in my RDS database, so even if I lose the plugins, as long as I reinstall them I don't lose their configurations.
I'm assuming in order to make my plugins persistent, I need to stick them in the root folder that I deploy the whole site with; but that feels like it could make updating the plugins tricky. (Or at least, a lot trickier than managing them through the admin panel--right now getting them into root means navigating everything through the command line.)
I guess I'm being lazy, but I'm just curious--is there a way to get close to the ease of functionality the admin panel offers both in terms of installing and updating plugins, while maintaining the persistence of bundling plugins in directly with your deployment?
Thank you!!
- Dominant language
- PHP
- Stars
- 166
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws-samples/eb-php-wordpress
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aws-samples/eb-php-wordpress#27 · 1 comment · 1 reaction ·
-
wp-content symlink Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aws-samples/eb-php-wordpress#24 · 16 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
aws-samples/eb-php-wordpress#21 · 9 comments · 2 reactions ·
All issues in aws-samples/eb-php-wordpress
Similar issues
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
UX
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ProfessionalWiki/NeoWiki#1525 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MagnaCapax/PMSS#949 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Automattic/static-site-importer#1829 ·