#HOW TO SET UP BITBUCKET DIGITALOCEAN INSTALL#
#HOW TO SET UP BITBUCKET DIGITALOCEAN CODE#
#HOW TO SET UP BITBUCKET DIGITALOCEAN FREE#

Git -work-tree=$TARGET -git-dir=$GIT_DIR checkout -f $BRANCH # 'Deploy' the branch we just pushed to a specific directory. + echo 'Push received! Deploying branch: $.' + + # Send a nice message to the machine pushing to this remote repository. + BRANCH=$(git rev-parse -symbolic -abbrev-ref $ref) + # Neat trick to get the branch name of the reference just pushed:

#HOW TO SET UP BITBUCKET DIGITALOCEAN FREE#

Inside of that block, we're free to do whatever we want, like copy the branch that was just pushed to a different directory: #!/bin/bash Ref - the Git reference of the branch just pushed. Newrev - the SHA for the new commit in the pushed branch. Oldrev - The SHA for the previous commit in the pushed branch. That's a bash while read loop with three parameters: While you're there, create a new post-receive hook: touch post-receiveĪnd paste the following bones in there: #!/bin/bash while read oldrev newrev ref If you cd into your neat-app-repo/hooks directory (this is one of the directories created when you initialized the bare repository), you should see a long list of *.sample Git hooks.

#HOW TO SET UP BITBUCKET DIGITALOCEAN CODE#

In our case, all we want to happen after our code is received is for it to be moved to a different directory and its dependencies installed. In short, this hook will allows to do something after code has been received by the repository on the droplet (ie. If you're unfamiliar with them, catch up. ssh /homeĬreate a post-receive hook file inside your newly created repository. We'll only be pushing to this repository, so -bare is the way to go.įor this example, kick this of by ssh-ing into your droplet, creating a neat-app-repo directory, and initializing that repository. A bare repository is one created without a working tree and used solely for sharing code - not working with it. Configure a Remote Repository on Your Dropletįirst, create a bare repository on your droplet. For the purposes of what I'm showing off here, just make sure you have a SSH access to your droplet, and that Git's installed on it.

Note that I'm not gonna get into the weeds of configuring a DigitalOcean or any other VPS. This post is basically me backing up and documenting all that I pieced together from experimenting and Googling. A single Git hook and a little local configuration meet all the needs noted above.

I wanted the option to control which branches would trigger a deployment to that droplet.Īs it turned out, the setup was less complicated than I had been expecting.

#HOW TO SET UP BITBUCKET DIGITALOCEAN INSTALL#

On that same push, I wanted to npm install the dependencies in my package.json.

On a git push, I wanted my code to be copied to my droplet.But thankfully, when I made the move to DO, my needs were relatively straightforward: They make that part of the job incredibly hassle-free. But there was one challenge I had yet to work out: setting up some sort of deployment process to get the code from my Git repository to my droplet. In just a short while, I was up and running these jobs with little issue. It was great, but eventually, the price:performance ratio offered became a little too unwieldy, and I chose to make a move from Heroku to DigitalOcean.Īlmost immediately, I was impressed. At first, when my needs were simpler, I used Heroku to run these jobs. I've been working on a project involving long-running, resource-intensive batch jobs in Node.

How to set up bitbucket digitalocean