-
Notifications
You must be signed in to change notification settings - Fork 7
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
807 delete lapis 1 and clean up #820
Conversation
2d9fec1
to
6276687
Compare
|
||
on: [push] | ||
|
||
env: | ||
DOCKER_IMAGE_NAME: ghcr.io/genspectrum/lapis-v2-docs | ||
DOCKER_IMAGE_NAME: ghcr.io/genspectrum/lapis-docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed that the running mpox instance on s0 has its own branch (ghcr.io/genspectrum/lapis-docs:br-mpox is currently running).
But there is also still ghcr.io/genspectrum/lapis-docs:public
running:
- Can we simply turn that off?
- Should we migrate that to the
lapis-v1
tag?
Another thought on this: Do we still need the public
branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But there is also still ghcr.io/genspectrum/lapis-docs:public running:
I'd leave it for now and have another cleaning round when we take LAPIS 1 open fully offline.
And also add the |
0ec961f
to
4f5a153
Compare
- move lapis2 to lapis - move lapis2-docs to lapis-docs - move siloLapisTests to lapis-e2e
4f5a153
to
3dbf6e8
Compare
GenSpectrum/LAPIS#820 renamed the image
GenSpectrum/LAPIS#820 renamed the image
resolves #807
Removes lapis 1 folders and renames lapis 2:
lapis2
->lapis
lapis2-docs
->lapis-docs
siloLapisTests
->lapis-e2e
Renames docker images of lapis2
lapis-v2
->lapis
lapis2-docs
->lapis-docs
The previous docker image
lapis-docs
has now a taglapis-v1
, so it can still be used. The mpox instance already uses its own tag for the documentationpr-mpox
.The README now has a general section in the base folder. For each folder there is a specific README. (Mostly copied over from the README in the lapis2 folder.
Necessary after merge:
lapis
docker image (0.2.2. and 0.2)PR Checklist
- [ ] All necessary documentation has been adapted.- [ ] The implemented feature is covered by an appropriate test.