@mmodell Not at a computer but isn't that just the tracking tag var?

@Negative24: Production isn't deployed via puppet anymore. I just need to set up labs instances to clone the deployment repo instead of the individual tags.

Ah, ok. (I'm a little bit curious of how the deployments are deployed; are they just pulled via git or something else?)

negative24: Scap

Clone rPHDEP Phabricator Deployment (master) into /srv/phab/, then run git submodule update and that's it!

For example:

sudo git clone https://gerrit.wikimedia.org/r/phabricator/deployment /srv/phab
cd /srv/phab
sudo git submodule update --init --recursive

Once that's done, future updates are as easy as , , , and . (pull → submodule update → restart apache → cake)

For maximum redundancy, these are the exact commands:

cd /srv/phab
sudo git pull
sudo git submodule update --recursive
sudo /etc/init.d/apache2 restart

@mmodell Thanks for your details (and icons to go with it :)).

Shouldn't sudo service apache2 restart be used instead of the init V script? (or does it even make a difference?)

In T117441#1843333, @Negative24 wrote:

@mmodell Thanks for your details (and icons to go with it :)).

Shouldn't sudo service apache2 restart be used instead of the init V script? (or does it even make a difference?)

Sure, service does the same thing as the init script though, in practice.

I tried it, phabricator was updated, but the design was broken, he tried to load this from http, not https.