updated maintaining drupal instructions #2223
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose / why
Updated the instructions for maintaining Drupal to add note about production, and address some permission issues that can happen when running Composer commands.
What changes were made?
Added a note to explain that updating Drupal should be done on a development site, then those updates can be built into an image for production.
Updated composer instructions to run as nginx user which makes new files owned by nginx.
Added a note about settings.php permission issue which happens when Mac users build a site based on the starter site (Islandora-Devops/isle-dc#306).
Verification
Installing a new site using
make starter
then running the new Composer update command should allow you to update your modules and everything should be owned by nginx. Using the old command would have new files owned by root.If you are on Mac you will get the error that settings.php can't be written to. Updating it's permissions so nginx can write to it should allow the composer update to succeed.
Interested Parties
Checklist
Pull-request Reviewer
Pull-request reviewer should ensure the following:
Person Merging
The person merging should ensure the following: