Allow custom user for executing commands #764
Closed
Conversation
This file contains 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
|
I don't have any further plans to customize the Sail user system. Feel free to fork or copy these files and edit them to suit your needs! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes:
I've made the user in
bin/sailconfigurable by setting theAPP_USERvariable in your project's.envfile. This allows you to set a different user as the one executing the sail commands. I set the default user to besailso that it won't break existing set-ups.Context:
Currently, sail commands are always executed using the
sailuser. However, I work with an existing Dockerfile setup which uses a different user and uses this user as the owner of the files in the container. This causes the sail commands to fail frequently due to permission errors.