-
Notifications
You must be signed in to change notification settings - Fork 24
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
Upgrade buttonweavers site to Ubuntu Xenial #2413
Upgrade buttonweavers site to Ubuntu Xenial #2413
Conversation
cgolubi1
commented
Nov 12, 2018
- Fixes Site upgrade #2398
- Replaces Upgrade buttonweavers site to Ubuntu Xenial #2412 and partially addresses the same issues as Site upgrade pull request #2411 --- we'll bring those changes in after the upgrade
I just opted to redo the branch so i didn't have to worry about merge issues and teasing out Shadowshade's changes that i had rebased in. I think this version has the right stuff in it:
The Vagrantfile changes:
I'm honestly not sure why that became necessary --- the default virtualbox hostname is now ubuntu-xenial, and it didn't like me setting it to sandbox early in the boot process. I don't think it's a big deal, though, because it's not going to break the running site. Either it'll work or it won't (and right now it does work on virtualbox and on the AWS replay site). Anyway, everything else is Shadowshade's changes from #2411 that we're not bringing in now, and we can tell that i got all of my changes from before, because the unit tests pass. |
Schedule:
|
Any reason this doesn't run CircleCI? |
Also, did you mean to include deploy/vagrant/ubuntu-xenial-16.04-cloudimg-console.log? |
1b169c4
to
6e70186
Compare
I don't know why it didn't have CircleCI before --- maybe the run was too old. Anyway, thanks for catching the logfile. I've removed it, and now it is running CircleCI. |
Looks good to me. This is ready to be merged whenever you're ready for it. |
We're at 5300 new and replayed games with this branch (plus the initial 13000 from what i believe to be the same code), so let's do this. |