We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
Running vagrant provision returns these errors:
svn: E120108: Unable to connect to a repository at URL 'http://core.svn.wordpress.org/trunk'
svn: E120108: Unable to connect to a repository at URL 'http://develop.svn.wordpress.org/trunk'
Looks to me like the repo does respond to their https versions - where would I change that for my existing develop and trunk sites inside vagrant?
Perhaps the issue is just that the http versions are down and will be back, but it would be nice to get them over https if one so chooses
The text was updated successfully, but these errors were encountered:
Here's what I did.
sudo vagrant ssh
svn relocate https://core.svn.wordpress.org/trunk
svn relocate https://develop.svn.wordpress.org/trunk
Will this persist now across vagrant up/down?
Sorry, something went wrong.
that will be fine on up/down and even when you re-run provision.
It would be nice to detect existing http checkouts and run svn relocate during provisioning now that we're using the HTTPS repositories.
At this point it's probably better to make sure this scenario is well documented either as a FAQ via #605 or in the wiki. We've been forced HTTPS a while now and I haven't heard much.
We should document this as part of the 1.3.0 changelog.
Document use of HTTPS SVN repositories in CHANGELOG
It looks like we did this in 9c1d453 :)
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
No branches or pull requests