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

Documented install with Docker #71

Open
4 tasks
super3 opened this issue Oct 14, 2014 · 10 comments
Open
4 tasks

Documented install with Docker #71

super3 opened this issue Oct 14, 2014 · 10 comments

Comments

@super3
Copy link
Contributor

super3 commented Oct 14, 2014

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:

  • Find someone to lead this issue
  • Refactor lunchbox to use Docker as a backend instead.
  • Make use of pushy-cat to automatically deploy and changes from the Github repos.
  • Write an idiots guide to deploying this system on a Digital Ocean Ubuntu x64 14.04 VPS.
@super3 super3 added the backend label Oct 14, 2014
@super3 super3 added this to the MetaDisk Beta 1 milestone Oct 14, 2014
@dingdreher
Copy link

+1

@EmergentBehavior
Copy link
Contributor

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.

@super3
Copy link
Contributor Author

super3 commented Oct 20, 2014

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.

@EmergentBehavior
Copy link
Contributor

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.

@super3
Copy link
Contributor Author

super3 commented Oct 20, 2014

So we need to pull in a freelancer that is quite capable with Docker, unless someone on our team can get this done.

@EmergentBehavior
Copy link
Contributor

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.

@super3
Copy link
Contributor Author

super3 commented Oct 20, 2014

Waiting on Brian to finish the new metachains.

@kylemanna
Copy link

I can help with Docker.

@super3
Copy link
Contributor Author

super3 commented Oct 21, 2014

That would be great. Take a look at the current documentation, and see if
you can get something running.

Shawn

On Tue, Oct 21, 2014 at 12:04 AM, Kyle Manna [email protected]
wrote:

I can help with Docker.


Reply to this email directly or view it on GitHub
#71 (comment).

Shawn Wilkinson
Lead Developer and Founder | storj.io
[email protected] | super3.org

@EmergentBehavior
Copy link
Contributor

@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.

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

No branches or pull requests

4 participants