We are a small development team and have recently started using bitbucket for a website development project. The repository contains all the files for the website (.html, .css, .png etc).
In our current work flow, after commits are pushed to the repository, the commiter copies his/her local copy of the repository onto our development server. As you can see, this is tedious and laggy. I wanted to automate this process so that each time the bitbucket repository is changed our web server updates to this copy. I am quite new to this, so any help/hints would be appreciated.
> We are a small development team and have recently started using > bitbucket for a website development project. The repository contains > all the files for the website (.html, .css, .png etc).
> In our current work flow, after commits are pushed to the repository, > the commiter copies his/her local copy of the repository onto our > development server. As you can see, this is tedious and laggy. I > wanted to automate this process so that each time the bitbucket > repository is changed our web server updates to this copy. I am quite > new to this, so any help/hints would be appreciated.
You can make Bitbucket "ping" a URL of your choice when changesets are pushed to it. This means that Bitbucket will make a HTTP POST request to your URL and that can then in turn trigger whatever update process you need. So you might setup
Personally, I would go for a simpler solution where I just add a script to the repository that the developers can execute that to upload the working copy to the web server as needed. That is simpler and more flexible since it lets you quickly deploy any revision on the server:
Personally, I would go for a simpler solution where I just add a script to the repository that the developers can execute that to upload the working copy to the web server as needed. That is simpler and more flexible since it lets you quickly deploy any revision on the server:
Can you please elaborate? Any tutorials/articles on how to achieve this?
hackologist <a.atee...@gmail.com> writes: >> Personally, I would go for a simpler solution where I just add a >> script to the repository that the developers can execute that to >> upload the working copy to the web server as needed. That is simpler >> and more flexible since it lets you quickly deploy any revision on >> the server:
> Can you please elaborate? Any tutorials/articles on how to achieve > this?
Well, you "just do it" :) You find a FTP client (as FTP is an insecure protocol you should see if you can use something better, such as SSH (secure copy)) that you can run from the command line and then make a script that invokes it.
If the server supports it, then I would go for rsync. Make a small script that calls rsync with the right parameters and then have the developers fire that away when they want to deploy their working copy on the server.
On Wednesday, March 9, 2011 7:28:25 PM UTC-5, hackologist wrote:
> Personally, I would go for a simpler solution where I just add a script > to the repository that the developers can execute that to upload the > working copy to the web server as needed. That is simpler and more > flexible since it lets you quickly deploy any revision on the server:
> Can you please elaborate? Any tutorials/articles on how to achieve this?
> On Wednesday, March 9, 2011 7:28:25 PM UTC-5, hackologist wrote:
>> Personally, I would go for a simpler solution where I just add a script >> to the repository that the developers can execute that to upload the >> working copy to the web server as needed. That is simpler and more >> flexible since it lets you quickly deploy any revision on the server:
>> Can you please elaborate? Any tutorials/articles on how to achieve this?
