Creating a Microservice
Once you log in to Ozone, select microservices on the left-side bar.
After clicking on microservices a modal window appears. Click on +New Microservice at the top-right corner.
If you already have a git repository linked, you can choose that from the dropdown, otherwise, you can click on the link shown below to link a git repository
![](https://docs.ozone.one/~gitbook/image?url=https%3A%2F%2Fdocs.ozone.one%2F%7Egitbook%2Fimage%3Furl%3Dhttps%253A%252F%252F3829750647-files.gitbook.io%252F%257E%252Ffiles%252Fv0%252Fb%252Fgitbook-x-prod.appspot.com%252Fo%252Fspaces%25252FAObcOkMb6sCSnSdcUOTm%25252Fuploads%25252FtfIr20vCYrdnFzvlmzGi%25252Fimage-20240415-094853.png%253Falt%253Dmedia%2526token%253Df7b03c0d-151e-4f78-8c5e-b59628855282%26width%3D768%26dpr%3D4%26quality%3D100%26sign%3Df5d058b3%26sv%3D1&width=768&dpr=4&quality=100&sign=c708d47f&sv=1)
If you already have a registry integration linked, you can choose that from the dropdown, otherwise, you can click on the link shown below to link the registry provider of your choice. This registry will be used to push and/or pull the required images
A microservice can run in different environments. There are three environments by default - Development, Staging, and Production.
But you can easily add more custom environments to fit your needs by clicking on the option that is shown below
Ozone relies on a Dockerfile to build and package your microservice. This file lists instructions for the Docker daemon to follow when building a container image. By specifying the Dockerfile location, Ozone understands how to construct the container image that will ultimately house your deployed microservice.
Last updated