Skip to content

These things live over at docspell/docker now#2911

Merged
eikek merged 2 commits intoeikek:masterfrom
pschichtel:cleanup/remove-docker-and-k8s
Jan 10, 2025
Merged

These things live over at docspell/docker now#2911
eikek merged 2 commits intoeikek:masterfrom
pschichtel:cleanup/remove-docker-and-k8s

Conversation

@pschichtel
Copy link
Copy Markdown
Contributor

I migrated the docker images, docker-compose and the kubernetes/* stuff (as a helm chart) over to https://github.com/docspell/docker as discussed. As to not confuse people, I'd like to remove the files in this repository.

@pschichtel
Copy link
Copy Markdown
Contributor Author

@eikek Where and how could we document the new location of all the deployment related things?

@eikek
Copy link
Copy Markdown
Owner

eikek commented Jan 9, 2025

Thank you so much @pschichtel 🙏🏼! I think we can update the docs and then I can re-deploy it. The doc changes can go agains the current-docs branch (code live in /website).

@pschichtel
Copy link
Copy Markdown
Contributor Author

@eikek so do I understand this correctly: I should do the website update as a separate PR against current-docs? Or should I retarget this PR?

@pschichtel pschichtel force-pushed the cleanup/remove-docker-and-k8s branch from c16ebca to da3a9ef Compare January 9, 2025 17:50
@eikek
Copy link
Copy Markdown
Owner

eikek commented Jan 9, 2025

@eikek so do I understand this correctly: I should do the website update as a separate PR against current-docs? Or should I retarget this PR?

I think it's better to do a separate PR against current-docs branch. This branch contains the website for the current version. After changes get merged into current-docs, I can redeploy the website and they are immediately visible. Would that work for you?

@pschichtel
Copy link
Copy Markdown
Contributor Author

sure

@pschichtel
Copy link
Copy Markdown
Contributor Author

can this one be merged then?

@eikek eikek added the chore label Jan 10, 2025
@eikek eikek merged commit 82d08a4 into eikek:master Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants