docker-hackmd
docker-hackmd copied to clipboard
hackmdio
Rename Repository as `codimd-docker`
From discussion about Renaming for codimd:
- https://github.com/hackmdio/codimd/issues/579
- https://github.com/hackmdio/codimd/issues/720
It's better we could rename this repo and related dockerhub auto build as codimd-docker
Besides, I would like to help to check any other parts also require renaming 💪
Reference: https://github.com/hackmdio/codimd/pull/881
I currently consider to create a new repo for codimd-docker. This would make contributions easier and the repo searchabe. Since right now it's a fork and default pull requests go to the upstream repo that is less maintained than this one.
I currently consider to create a new repo for codim-docker.
Also I would suggest mark this repo as archived (read-only) and
edit README.md to direct visitor to new repo hackmd/codimd-docker
UPDATE: One bad news is the docker automated build repo CANNOT be migrated.
It is always chained to hackmdio/docker-hackmd repo.
Yes, that was definitely part of the plan.
By the way we don't build images on docker hub for months now, we are only pushed there.
We may create a new repo there as well. I currently also consider to use quay.io instead since I use it for my other setups as well and it has some nice features, like security scans, included by default. (Not sure if there is an image size limit)
I added a new repository under https://github.com/hackmdio/codimd-container
This is the first step. For now we will stay with the current docker repository, moving away from it, will come soon, too :)
Thanks for reminding me about this!
I'm not too familiar with docker, is there a way to push one more update to "this" repo, which contains a note for users or something like that? The renaming is very easy to miss, if you're not too involved with a project.
I consider to provide a commit that will break updates, yes.
Basically removing the whole repository content. Except for a note pointing to the new one