Publishing services

Once your service has been created and tested, it's time to publish it to the regsistry and get it deployed!

Publishing services is the final step in preparing a service for deployment. Publishing services to the registry allows Architect to index it in relation to it's cited dependencies and ensure that dependencies are resolved when executing remote deployments.

Publishing a single service

The easiest way to publish a service is to run the push command and cite the path to the services source. Architect will execute docker build, tag the artifact with the service configuration details, and push the resulting artifact to Architect's registry associted with your account. Once in the registry, you'll have full control over the service, the environments it can be deployed to, and the co-workers that will be allowed to pull it down and reference it in local tests.

architect push -s ./path/to/service --tag "some-tag"

Publishing multiple services

If you happen to be developing multiple services locally and wish to push multiple artifacts at the same time, you can alternatively specify the path to the environment config you use for debugging and our CLI will identify all the local services that can be pushed in tandem:

architect push -e ./path/to/env-config.json