* Update README.md
* We don't want to use the netbox-community pull-request template
* Update container building workflow
* Only build amd64 images
* Add our 'oxcert' branch as equivalent to upstream's 'release' branch
* Tag the version of the container as OxCERT's modification
This is just for the netbox container: the underlying netbox version
will come from upstream
* Build own own images and push to ghcr.io
* Only build amd64 images
* Only push images to GitHub Container Registry for the OxCERT organization
* Refer to our private copy in the GitHub Container Registry ghcr.io
* Use ghcr.io/oxcert/netbox for all netbox images
Build and push to this repo. Read from it with docker-compose
* Make releases relative to the 'oxcert' branch
rather than upstream's 'release' branch. This is a different workflow
than used in any of our other repos, where PRs, changes, etc. are
first merged into a 'develop' branch, and the release process is to
merge accumulated changes into the main 'oxcert' branch.
Tag names for releases should follow whatever upstream is using with
"-oxcert" appended.
* Re-add the pull-request template
But in a very cut-down form. We don't have an issue tracker on this
repo, and we assume the intentions and motivations for any PR will
have been discussed within the team already. We do, however, want all
PRs to be against the 'develop' branch, in parallel to upstream's
workflow.
* On second thoughts, set container version to 1.0.0
This is OxCERT's version 1.0.0 of the containerized Netbox image which
is basically the same as the 2.7.0 netbox-community equivalent.
* Fix typo from upstream
Function should have been called `git_rebase()` rather than
duplicating the name of `git_merge()`
So we end up with just the arm64 images in ghcr.io repository, since
they are the slowest to build.
Resynchronise the 'platforms' section in the workflow with
upstream. It's not a list of architectures, one per list entry. It's
a single list entry mentioning all architectures.
* Update README.md
* We don't want to use the netbox-community pull-request template
* Update container building workflow
* Only build amd64 images
* Add our 'oxcert' branch as equivalent to upstream's 'release' branch
* Tag the version of the container as OxCERT's modification
This is just for the netbox container: the underlying netbox version
will come from upstream
* Build own own images and push to ghcr.io
* Only build amd64 images
* Only push images to GitHub Container Registry for the OxCERT organization
* Refer to our private copy in the GitHub Container Registry ghcr.io
* Use ghcr.io/oxcert/netbox for all netbox images
Build and push to this repo. Read from it with docker-compose
* Make releases relative to the 'oxcert' branch
rather than upstream's 'release' branch. This is a different workflow
than used in any of our other repos, where PRs, changes, etc. are
first merged into a 'develop' branch, and the release process is to
merge accumulated changes into the main 'oxcert' branch.
Tag names for releases should follow whatever upstream is using with
"-oxcert" appended.
* Re-add the pull-request template
But in a very cut-down form. We don't have an issue tracker on this
repo, and we assume the intentions and motivations for any PR will
have been discussed within the team already. We do, however, want all
PRs to be against the 'develop' branch, in parallel to upstream's
workflow.
* On second thoughts, set container version to 1.0.0
This is OxCERT's version 1.0.0 of the containerized Netbox image which
is basically the same as the 2.7.0 netbox-community equivalent.
* Fix typo from upstream
Function should have been called `git_rebase()` rather than
duplicating the name of `git_merge()`
We now serve Netbox with an nginx-unit instance instead of Gunicorn.
This allows us to get rid of the extra Nginx container because Unit is
also serving the static files. The static files are now collected at container
buildtime instead of every startup.
This commit adds links to the _New Issue_ section of Github.
The intention is to provide more hints where to get help and
further reduce the amount of Github issues that can not be
acted upon.
The old version of "build-branches.sh" skipped the pushing of images when one of
them didn't change its sources. When looking at the Netbox branches I noticed
that the "master" branch only changes when there is a new release. Because we
build the new releases anyway in "build-latest.sh" that leaves "develop" and
"develop-*" which change regularly. The new script "build-next.sh" is responsible
for building "develop-*" as the next major release of Netbox. The build of
"develop" is moved to the Github Action build matrix. This has the additional
advantage of being faster because more builds are done in parallel.
