Deploying from an Existing Docker Registry
Deploying your Docker Image
To deploy your application, first navigate to the Launch tab, where you will see three types of applications to deploy: web, worker, or job. To understand the difference between these three application types, see the description of the types of applications. After selecting your application type and selecting Launch Template, you should select the Docker Registry option:
Next, you can either select a public or private Docker image to deploy from:
Private
Public
To deploy from a private image, make sure you have linked a private registry. Then, simply select the image repo and tag you would like to use:
Select “Continue” after specifying your image.
Under Additional Settings, you can configure remaining options like your service’s port and computing resources. Once you’re ready, click the Deploy button to launch. You will be redirected to the cluster dashboard where you should see your newly deployed service.
Updating your Docker Image
Manual Updates
To update the Docker image which your application is running, open the application on the Porter dashboard. If your Docker image has a unique image tag, you can navigate to the Settings tab and select a new tag for your image:
If your Docker image tag is latest
(or you re-use the same image tag for different images), there are different options depending on if you are running an web/worker or a job:
Web/Worker
Job
If running a web or worker application, navigate to the Main tab and hit “Deploy” with no configuration changes:
This will re-pull the image by default.
Programmatic Updates
To programmatically redeploy your service (for instance, from a CI pipeline), you will need to call your service’s custom webhook. You can find your webhook by expanding your deployed service and going to the Settings tab.
Make sure to replace the YOUR_COMMIT_HASH
field with the tag of your Docker image.