You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2020. It is now read-only.
Configuring a nexus instance can happen in multiple ways, AFAIK, but in any case, typically a user would want to be able to configure nexus at first bootstrap. For that s2i is a nice mechanism.
You can allow the nexus container (or create a new variant) to get from a git repo the nexus configuration, whether that is the nexus.xml file or just some files to allow to bootstrap/provision nexus appropriately when building the container.
Typically adding a mirror, and adding that mirror to the public group is something that will be always done. Additionally be able to bootstrap users, hosted repos, proxy repos, groups, add repos to groups.
The workflow could be like this:
I deploy a nexus-s2i image, and provide my git repository for the nexus config. In this repo I have 2 json files to create a proxy repo and to add the repo to the group. When the container is built it will include already by default this configuration.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Configuring a nexus instance can happen in multiple ways, AFAIK, but in any case, typically a user would want to be able to configure nexus at first bootstrap. For that s2i is a nice mechanism.
You can allow the nexus container (or create a new variant) to get from a git repo the nexus configuration, whether that is the nexus.xml file or just some files to allow to bootstrap/provision nexus appropriately when building the container.
Some helpful scripts can be found here: https://github.com/jorgemoralespou/nexus-ose/tree/master/nexus/nexus3-container/usr/local/bin
Typically adding a mirror, and adding that mirror to the public group is something that will be always done. Additionally be able to bootstrap users, hosted repos, proxy repos, groups, add repos to groups.
The workflow could be like this:
I deploy a nexus-s2i image, and provide my git repository for the nexus config. In this repo I have 2 json files to create a proxy repo and to add the repo to the group. When the container is built it will include already by default this configuration.
The text was updated successfully, but these errors were encountered: