Private repository consequences/solutions

[johanvdw]

Some consequences of the repository being private:

• No new documentation on https://inbo.github.io/niche_vlaanderen/
• No automated tests on commit
• No automated publishing on pip - leads to the question whether this should still be on pip or not. It currently still is.
• We should also check what is on zenodo and whether this can still be public

There are solutions, but they take some time so if there is a possibility that we can reopen the repo I would like to postpone them for now. Note that the first two (website and pip repository) are relatively easy, so we can also decide to do only that and skip automated builds.

• we can publish documentation either manually or automatically (if we have a github action runner, see next) to an S3 bucket which we open as a website. Something similar can be done for the pip archives. This would lead to something like eg https://niche-vlaanderen-docs.s3-website.amazonaws.com.
• Installing via pip if we take the package from pypi could proceed by running:
• pip install --extra-index-url https://niche-vlaanderen-pip.s3-website.amazonaws.com niche_vlaanderen
• For automating actions, it is possible to run github actions through a self-hosted runner. This is however somewhat complicated to set up, and unless an infrastructure is already in place for other inbo projects, I think we may skip this.

[johanvdw]

TODO: On the short term: take documentation website and/or pip offline

[johanvdw]

The documentation has been taken offline: https://inbo.github.io/niche_vlaanderen/ . Feel free to improve wording.

[johanvdw]

From 2023-01-01 we can publish niche_vlaanderen online.