-
Notifications
You must be signed in to change notification settings - Fork 4
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 (Docker) repository to organisation? #14
Comments
Yeah I think that would be a good idea. I'm out of town for the rest of the weekend, so I'm just going to give you access to the Docker repo in the mean time. |
@blueyed I was surprisingly able to create the organization "testbed", so we could have |
And thanks a lot for all the work you put in to this repo! Sorry I wasn't around during all your activity. |
This also adds a separate Dockerfile for the tests, making the example work by itself. Ref: https://hub.docker.com/r/testbed/vim/ Ref: Vimjas#14
btw: https://github.com/testbed/ is taken, but looks interesting.. ;) |
I cannot push to https://hub.docker.com/r/testbed/vim/. My Docker Hub username is "blueyed". |
When you're at it, please also add an user for automatic pushes (#19). We would encrypt its auth in a secret for Travis then. |
@blueyed I added you to a group and forgot to add that group to the repo. I just made you an owner in the org. I'm a little confused by Docker Hub's ACLs. Hopefully you'll have free reign on it and can add repositories. |
Yay, pushed to https://hub.docker.com/r/testbed/vim/. |
Closing this, thanks! For the future:
|
This also adds a separate Dockerfile for the tests, making the example work by itself. Ref: https://hub.docker.com/r/testbed/vim/ Ref: #14
@blueyed It just came to mind to look at this again. It seems that |
I'd like to be able to push new base images myself, and therefore think it makes sense to move this repo to an org and/or provide access to the Docker repository (https://hub.docker.com/r/tweekmonster/vim-testbed/) to me.
The text was updated successfully, but these errors were encountered: