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

807 delete lapis 1 and clean up #820

Merged
merged 2 commits into from
Jun 3, 2024
Merged

Conversation

JonasKellerer
Copy link
Contributor

@JonasKellerer JonasKellerer commented May 28, 2024

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 tag lapis-v1, so it can still be used. The mpox instance already uses its own tag for the documentation pr-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:

PR Checklist

- [ ] All necessary documentation has been adapted.
- [ ] The implemented feature is covered by an appropriate test.

@JonasKellerer JonasKellerer force-pushed the 807-delete-lapis-1-and-clean-up branch 9 times, most recently from 2d9fec1 to 6276687 Compare May 29, 2024 11:44
@JonasKellerer JonasKellerer marked this pull request as ready for review May 29, 2024 11:46

on: [push]

env:
DOCKER_IMAGE_NAME: ghcr.io/genspectrum/lapis-v2-docs
DOCKER_IMAGE_NAME: ghcr.io/genspectrum/lapis-docs
Copy link
Contributor

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?

Copy link
Member

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.

@fengelniederhammer
Copy link
Contributor

* [ ]  adds semVer tags to `lapis` docker image (0.2.1.)

And also add the 0.2 tag.

@JonasKellerer JonasKellerer force-pushed the 807-delete-lapis-1-and-clean-up branch 2 times, most recently from 0ec961f to 4f5a153 Compare June 3, 2024 06:19
- move lapis2 to lapis
- move lapis2-docs to lapis-docs
- move siloLapisTests to lapis-e2e
@JonasKellerer JonasKellerer force-pushed the 807-delete-lapis-1-and-clean-up branch from 4f5a153 to 3dbf6e8 Compare June 3, 2024 06:26
@JonasKellerer JonasKellerer merged commit 46a0efa into main Jun 3, 2024
6 checks passed
@JonasKellerer JonasKellerer deleted the 807-delete-lapis-1-and-clean-up branch June 3, 2024 06:33
fengelniederhammer added a commit to loculus-project/loculus that referenced this pull request Jun 17, 2024
corneliusroemer pushed a commit to loculus-project/loculus that referenced this pull request Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Delete LAPIS 1 and clean up
3 participants