-
Notifications
You must be signed in to change notification settings - Fork 23
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
Documented install with Docker #71
Comments
+1 |
Pushy-cat would have to be modified to deploy dockers. I'm thinking we should use ansible to construct a new docker container (when things change), then a modified push-cat could deploy the dockerized container. |
Well I think everything should be deployed from the source, rather than static containers. Just need to be able to pull in the dependency list from the repo and go. If we keep everything important on the blockchain, shouldn't cause any problems. |
I meant that ansible would build everything from source each build, put together an updated docker container, then someone could just pull the docker container down and load it up. They could do it from source too but would defeat purpose of having a docker container. |
So we need to pull in a freelancer that is quite capable with Docker, unless someone on our team can get this done. |
I could start on it after the dash and get the process going, but i don't think it makes sense to formally release a dockerized app until some of the back-end issues are fixed and the new front-end is tested. |
Waiting on Brian to finish the new metachains. |
I can help with Docker. |
That would be great. Take a look at the current documentation, and see if Shawn On Tue, Oct 21, 2014 at 12:04 AM, Kyle Manna [email protected]
Shawn Wilkinson |
@kylemanna: Great! Ideally, we should be able to build a new dockerized container when we push a new release. I was thinking of using Ansible for that, but if you're comfortable with something else, give it a go. We're trying to migrate away from Chef. |
Currently we have been using lunchbox to deploy MetaDisk scripts to a VPS. This has proved quite ineffective, and difficult to use. Instead we would like to use Docker, which will allows us to run some of the modules naively.
Tasks include:
The text was updated successfully, but these errors were encountered: