4 ms·
if i understand the post correctly, then i'm using github as the hub, with copies checked out locally and on the web server. whoa--- how else do people deploy
by diN0bot 17y ago
if i understand the post correctly, then i'm using github as the hub, with copies checked out locally and on the web server.
whoa--- how else do people deploy to live sites? i can't imagine not using version control. or am i missing some nuance of the situation?
- prodigal_erik 17y ago"yum install". We write a .spec file for each service we deploy, and when we're ready to deploy we compile and package the current release branch. That way the OS package manager knows what's installed where, whether any dependencies also need to be installed or upgraded, and whether local edits should be preserved or renamed. I've never understood how "git pull" is supposed to configure a production server correctly. What do people do, put /usr/bin and /usr/lib64 and /etc in git?
- vog 17y agoAlthough it is usually not done with /usr/*, it is quite common to put a server's /etc under version control. But that's for administrative control, and is usually completely separate from the web application. However, it is quite common to use rsync for deployment of everything: system, application, etc. from test to production, without any version control needed. This works especially well when using vservers.
- diN0bot 17y agoi'm just updating a web app in /var/sites. git pull followed by an alias to a few commands to rebuild templates and reload the server. i guess there are at least two views of updating web servers: the servers themselves and the web application. the latter is a lot more self contained. i forgot about the former. i set that up once, backed it up, and pray that i don't have to touch it again :-p