Deploying websites with Subversion
I think I'm going to move to Subversion all the websites which still aren't versioned. It's so annoying to change things locally, test locally, then you want to upload them to the server and there's always some change which it's not updated and booooom!
With SVN (Subversion) it's much easier. You continue building your stuff locally and when you're happy with it, check it into your Subversion server. Then you log into your hosting server with ssh, and in your /web directory do something like svn co http://mysubversionserver/project/trunk . - that will associate the /web directory with the subversion repository path /project/trunk. Meaning that each time you do changes and commit them to SVN, you can get all the changes rolled to your server by simply connecting with ssh and running svn up in the /web directory.
Obviously for doing this you need a hosting account with ssh access. Most of them do not have such thing, and I really can't understand how could I survive without ssh access before. Even for simple things such as deleting a directory, ftp's and sftp's are terribly slow :-)
There's more sophisticated people which are using build makers like ant or the famous capistrano to deploy stuff but for the moment I still don't need that degree of complexity; it's not worth the effort yet.
Manuel J. Recena Soto
20070221
Hola Sole:
Mi recomendación es que antes de pasar a producción una nueva release crees su correspondiente etiqueta, y que el contenido que pases a producción sea exactamente (tras hacer un export) el contenido de dicha etiqueta.
Un saludo
HeV
20070221
Es una muy buena opción pero tampoco te confies. En mi anterior trabajo nos iba de p.m., aquí ahora mismo cada vez que me actualizo me da problemas y me toca estar corrigiendo muchos ficheros manualmente, afortunadamente lleva un asistente para ello :P
sole
20070221
With "websites" I meant my personal websites. Creating tags and all that… I think it's a bit overkill.
Manuel J. Recena Soto
20070221
Hola Sole:
No te creas, te cuesta muy poco y una vez que te acostumbras, sólo tiene ventajas.
Uno de los problemas que vengo observando en los últimos meses es el uso incorrecto de los sistemas de control de versiones, concretamente con Subversion.
He podido comprobar como hay gente que está desarrollando un proyecto java (especifico esto para informar que son documentos de texto, no binarios) bloquea los fuentes en los que está trabajando y te dice: "…es para que no me los toquen otros compañeros…" y sospecho que simplemente para evitar resolver los posibles conflictos. Entiendo que cuando no se tiene experiencia, un merge de un poco de miedo, pero depende de lo metódico que sean los programadores.
Cuando tengan que enfrentarse a un merge tras una refactorización…..
Un saludo
miguev
20070221
You may as well be interested in managing your SVN repository through SSH (Spanish link ;-))