-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Add /srv/vvv #2328
base: develop
Are you sure you want to change the base?
WIP: Add /srv/vvv #2328
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and no errors
@Mte90 that shouldn't have happened, looks like there's still work to be done here |
As I can see that folder get root permissions instead the others have vagrant/vagrant: I think that a chown when the folder is created should be enough @tomjn |
I think that is the case that someone else test that PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. This still fails with the SCP error (actually, the only change made after the SCP error was discovered was a merge).
I will do some tests for this to moving on, I just forgot it... |
So I tested it and a
|
converted this to a draft, I want to see the end result of the vagrantfile changes before adjusting this |
Switch from
/vagrant
to/srv/vvv
Checks
develop
branch not thestable
branch.