Skip to content
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

Dockerize pairs2 #71

Open
jaybobo opened this issue Oct 11, 2016 · 5 comments
Open

Dockerize pairs2 #71

jaybobo opened this issue Oct 11, 2016 · 5 comments

Comments

@jaybobo
Copy link
Member

jaybobo commented Oct 11, 2016

@BrianLees has some ideas about how to make it easier for all attendees to contribute without experiencing the pain of setting up an environment.

  • cloud9/gitlab
  • or docker
@TravisSperry
Copy link

Vagrant has been super easy to work with, but I've never worked with Docker.

@jaybobo
Copy link
Member Author

jaybobo commented Oct 11, 2016

Sorry I should have added extra context. Vagrant has worked just fine for Linux users but some PC users had difficulty so this conversation stems from that...just a thought.

https://docs.docker.com/engine/installation/windows/

@TravisSperry
Copy link

That makes sense. Is it possible to Vagrantize and Dockerize? Or would that not make sense?

@BrianLees
Copy link

You can do either.There was actually a project by the vagrant team that would do both (Otto if you want to look out up) but unfortunately they have stopped work on it.

@jcwimer
Copy link

jcwimer commented Oct 17, 2016

I could dockerize the development environment for linux users who do not want to virtualize then I could set up vagrant files for osx and windows users. The vagrant environment would use linux and then docker would be used inside the virtual linux os with a host only network so they could access 'rails s'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants