next »

[arms]

im curious what methods/systems of deploying your projects/work whatever across different enviroments/servers people are using.
im looking at fabric which is a python project based on the ruby project capistrano. it's basically a way to automate repetitive tasks across different enviroments.
do you do everything manually, use a shell script, some fancy enterprise solution, your IDE, etc.?

[nutballs]

i work live, because I am a loser and love getting phonecalls from clients that seem to ALWAYS be surfing the site while I am working on it. 

then i download backups every so often. This is all about to change however to have an actual dev machine, and then deploy from there. So... I am actually interested in this as well.

[perkiset]

I work live as well. I have developed my own form of making sure I have my sh!t wired tight before I click "Save."

Then there's also the notion that, for the 5 seconds that I'll see an error on the page before I go correct it, no one else will see it.

Lastly, if I have an entirely new system that must come up, I'll put the whole website on another domain and work it there till I am satisfied with its operation.

[arms]

i work local then upload changes. so i'm looking to automate this.
so far from what i see looking at fabric, its like a higher-level shell scripting in python for sftp'ing to remote servers, checking out of version control, executing command on the server etc. for anyone who is proficient in shell scripting it would really be of use. for me or anyone who doesn't know shell scripting it could be useful.

[walrus]

I usually keep some sort of source repository handy (svn)  and I make all the changes localy, then test the hell out of it and in the end upload the changes. I try to keep a local mirror of the working server. Sometimes things still get broken when I upload to the live server.

If I need to deploy to a lot of servers... bash/something.

[vsloathe]

For a couple sites, I have mirrored local copies and BASH scripts that push the saved local versions out to production.

For some older ones, I have them on SVN. For the newest ones, I use Git.

Seriously guys? LIVE? That honestly makes me a little skeeved. Last week if either nutballs or perkiset came to me and said "yeah, I don't use a versioning system or a release cycle" I would have said "LOL, seriously though". I thought versioning systems and revision control were pretty much just *what you do* as a competent programmer.

[arms]

how are you finding git?
i'm using svn but i keep reading how git is going to change to world.
i work alone so i don't need fancy revision control just basically so i can roll back if i fuck everything up. what i don't like about svn is i have to type a full path to my local repository and how it's all one big repo.

[vsloathe]

I like Git a lot, or I wouldn't have switched

It's robust, fairly straightforward, and pretty durned fast. I'm sure there are hundreds of guys who, while not necessarily more articulate than I, have better been able to lay out the pros/cons of Git/SVN/CVS et al.

[walrus]

Have you seen this ? (I don't think it's functional, but it's a weird/nice idea)
http://code.google.com/p/gittorrent/

[vsloathe]

Very interesting, walrus.

Thanks for that.

[arms]

I like Git a lot, or I wouldn't have switched

It's robust, fairly straightforward, and pretty durned fast. I'm sure there are hundreds of guys who, while not necessarily more articulate than I, have better been able to lay out the pros/cons of Git/SVN/CVS et al.

i just settled on bzr. i played with git a bit but i found the bazaar documentation very clear and helpful, even giving examples of different workflows for different situations. the commands feel a little more intuitive coming from svn.