Using Appsody? Add Nexus Repository as Your Default Repository Manager

At Sonatype we’re continually looking for ways to improve development and simplify your tech stack. With the birth of Kubernetes, companies are trying to solve the problem of building and deploying faster and at scale. Nexus Repository now integrates with Appsody, giving you the ability to add Nexus Repository to your Java Microprofile and Node JS Express stacks.

Appsody is designed to help you develop containerized applications for the cloud. With Appsody, you can build applications that are ready to be deployed to Kubernetes without being an expert on the underlying container technology.

If you’re responsible for defining standards for application runtime environments such as software levels, Appsody allows you to control the stacks that your developers use. You can define a set of technologies that are configurable, reusable, and already infused with cloud-native capabilities to ensure and maintain standards, consistency, and reliability.

One specific element that you can define and configure is your repository manager.

With an Application Stack, the owner of each stack can provide a default repository manager, force the use of a specific repository manager instance, or block the use of a repository manager.

The current Java Microprofile and Node JS Express stacks restrict repository access, so if you want to use Nexus Repository you’ll need to create your own stack. You can start by copying and customizing an existing stack rather than starting from scratch.

Click here for the guide with step by step instructions to configure a Nexus Repository for both a Java and Node JS stack within Appsody.