WIP - Update permissions for pm2, laravel app-release commands #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
greyvugrin
commented
Jan 25, 2024
|
|
||
| ## Make Logs Directory | ||
| sudo mkdir -p "$REPO_ROOT/$LARAVELLOGSFOLDER_LOCATION" | ||
| sudo mkdir -m 775 -p "$REPO_ROOT/$LARAVELLOGSFOLDER_LOCATION" |
There was a problem hiding this comment.
this will make the end directory have the correct permissions, but not the full tree. hence the looping afterward
|
Reminder: You mentioned that you may still have log permission issues and this may not solve it? |
amurrell
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updated pm2 & laravel release commands.
Fixed an issue where custom log paths like
DockerLocal/logswould not have the OWNER_USER:OWNER_GROUP applied at all folder levels.Caused issues: