Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.localops.co/llms.txt

Use this file to discover all available pages before exploring further.

Deployment can be started for a service either manually from LocalOps console or by pushing new code to the configured service repo and branch name.

​
Automatic deployments

Whenever your team pushes new code to Git repository, LocalOps can automatically pull the hcanges, build them as Docker images very quickly and deploy seamlessly on the corresponding environment. If you have a local development environment for the git repository configured for the given service, you can simply follow these steps to start deployment. 
$ git checkout <branch-name>
$ ..add commits
$ git push <remote-name> <branch-name>
If your GitHub organization doesn’t allow direct git push on the branch, you can ask your team to raise pull requests (PRs) targeting the configured branch name of the service. If you merge the PR, a new deployment will start in LocalOps with the latest commit on that branch. Or if you directly edit files in Github website and make new commits on the configured branch name of the service, a new deployment will start. A new build & deployment process will start in either of these cases. Navigate to “Deployments” tab within the same service section to see the logs.
For commits to get automatically deployed, the github user who made the commits, must be added to your LocalOps account as a user. And they must have linked their Github profile with LocalOps from inside Profile settings: https://console.localops.co/profile

​
Manual deployment

  1. Click on “environments” on the left
  2. Navigate into the relevant environment
  3. Navigate to Services tab
  4. Click on the service where you want to trigger new deployment
  5. On the top right corner, click on “Deploy”.
  6. Verify the commit details put on the confirmation window
  7. Click on “Confirm” to proceed.
A new deployment will start. Navigate to “Deployments” tab within the same services section to see the logs.