Deploy a website using git in Ubuntu • Hacker News Board

Re: Deploy a website using git in Ubuntu

#11

Post by sciurus » Tue, Jun 05, 2012, 5:33 AM UTC

Having a bare repository on the same server as a "deployment" repository, where the repositories are configured to

1) automatically pull changes into the deployment repository from the bare repository

2) automatically push changes into the bare repository from the deployment repository

feels like a hack. Maybe git needs a concept somewhere between a normal and a bare repository, where the files are checked out but aren't teated like a normal work tree, i.e. you can't commit anything, and on a merge any local changes are thrown out?

Re: Deploy a website using git in Ubuntu

#12

Post by carbocation » Tue, Jun 05, 2012, 5:33 AM UTC

Don't use this approach; your http-accessible directory does not need a git repo living inside it.

Just have your script export the repo contents by using `git archive` —thereby exporting just the files you created, without any git machinery—instead of this approach.

Re: Deploy a website using git in Ubuntu

#13

Post by haroldp » Tue, Jun 05, 2012, 5:39 AM UTC

I do something like this and like the workflow quite a bit. I copied it from this guy: http://joemaller.com/990/a-web-focused-git-workflow/

In the comments there's also a nice set up for running a staging server from the same hub repo.

Re: Deploy a website using git in Ubuntu

#14

Post by pavanky » Tue, Jun 05, 2012, 5:42 AM UTC

for the love of technology, stop with the titles that say do XYZ in Ubuntu. Pleaese use Linux instead.

I think everyone knows how to use a package manager and find the equivalents for 'apt-get install'

Re: Deploy a website using git in Ubuntu

#15

Post by pindi » Tue, Jun 05, 2012, 6:18 AM UTC

ceol wrote: post #2

Great article! My apologies if this is too off-topic, but it's interesting to see everyone's virtualenv setup. I normally have my project/site/app in my environment folder, so it looks something like: projectenv/ bin/ include/ lib/ project/ but I've also seen (as is the case in the OP's example): project/ env/ __init__.py database.py ... or even having a separate folder for all environments: envs/ env1/ env2/ ... pro…

I don't think there's a "right way", but I prefer the second format. In the first format, it's difficult to delete and recreate the entire virtualenv without also deleting your project files. And in the third, your environments are unnecessarily separated from their respective projects.

Re: Deploy a website using git in Ubuntu

#16

Post by mappu » Tue, Jun 05, 2012, 6:49 AM UTC

pyre wrote: post #9

mappu wrote: post #7

Is git push atomic? I'm reaching the point with a PHP application where enough people are using it at any one point, every time i push an update (using lftp --mirror over sftp) someone gets caught in the crossfire. My next step is deploying to a temporary folder and swapping symlinks around, but if git/hg can do an atomic update that would be much simpler.

I do not believe that checking out all files in a repository is supposed to be a single atomic action in either git or hg.

I didn't think so. Thanks for the clarification.

Re: Deploy a website using git in Ubuntu

#17

Post by lnguyen » Tue, Jun 05, 2012, 7:33 AM UTC

binarydreams wrote: post #6

DHowett wrote: post #5

Earlier quoted context omitted.

This could be solved reasonably well with ACLs. Give the git user selective write to the tree rooted at /srv/www/helloworld.

but the plan/aim is to make it all very simple to setup (even for noobs :)). cmon, ACL knowledge is not something wide spread. So, we need to keep things simpler!

Sometimes there's a limit to how simple something can be. And sometimes you don't want to/shouldn't hide the complications.

I think that introducing users to ACLs, permissions and security is appropriate at this step. You can have a script/process in place that can take care of this but you should explain what's going on and why. Because if there's a security issue, they can at least have some kind idea of what happened.

Re: Deploy a website using git in Ubuntu

#18

Post by kijin » Tue, Jun 05, 2012, 8:31 AM UTC

mappu wrote: post #7

Is git push atomic? I'm reaching the point with a PHP application where enough people are using it at any one point, every time i push an update (using lftp --mirror over sftp) someone gets caught in the crossfire. My next step is deploying to a temporary folder and swapping symlinks around, but if git/hg can do an atomic update that would be much simpler.

If you have APC (which you should), you can turn off apc.stat to make PHP ignore changes to actual files and keep serving scripts from the (now stale) opcode cache. Depending on the structure of your app, this might be good enough to keep things running smoothly during the second or two that it takes for git to update the working tree. When you're done, atomically clear the opcode cache. Turning off apc.stat also helps your pages load faster.

Re: Deploy a website using git in Ubuntu

#19

Post by sp332 » Tue, Jun 05, 2012, 11:30 AM UTC

pavanky wrote: post #14

for the love of technology, stop with the titles that say do XYZ in Ubuntu. Pleaese use Linux instead. I think everyone knows how to use a package manager and find the equivalents for 'apt-get install'

Different distros have different filesystem layouts, different package managers, even different package names. It's useful to have one worked example. Especially when Ubuntu works hard at being accessible to beginners, it makes sense for that example to be Ubuntu (since the users most likely to need hand-holding are on Ubuntu).

Re: Deploy a website using git in Ubuntu

#20

Post by knowshan » Tue, Jun 05, 2012, 1:42 PM UTC

A comment and a question: 1. Unless you are going to make commits or any changes in the deployment directory (not recommended), you don't need a git repository there - 'git checkout -f' to GIT_WORK_TREE should work as a post-receive hook there 2. Would your post-receive hook deploy for a push done to any branch or a specific branch??