-
Notifications
You must be signed in to change notification settings - Fork 180
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
move uproxy-docker here #2841
move uproxy-docker here #2841
Conversation
osx now uses docker-machine
output the vm ip on osx
a script to create a cloud instance
update firefox download logic for new download system
replace passwords in invite codes with private keys
* update paths to account for new uproxy output folder
* move to unbranded firefox builds
Accept public key (-k option) for install-cloud scripts
… move to alpine for smaller image (#106)
👍 for this change, although it seems like we might need to wait a while before we remove the uproxy-docker repo, since users currently have versions of uProxy installed which refer to install-cloud.sh in that repo right? It seems like maybe the next step will be to change https://github.com/uProxy/uproxy-cloud-install/blob/master/src/digital-ocean-installer.ts#L48 to refer to the new location |
Yes! It's not quite time to update all the references to uproxy-docker - but I do agree that should be next and should happen soon. Thanks for reviewing, I know this wasn't very easy to examine :-) |
This copies across all of https://github.com/uProxy/uproxy-docker to a new folder named
docker
.This will make it a lot easier to develop changes affecting both repos. Motivation for doing this now is to make Node.js development easier.
The files are unchanged except for the
-p
option ofrun_pair.sh
andrun_cloud.sh
which changes from a string flag meaning "pull the zork from the client at this path" to a boolean flag meaning "use the Zork in this client".@jab FYI
This change is