2010/11/3 Ashar Voultoiz hashar+wmf@free.fr:
but I am not going to do anything without having proper documentation about the 2010 way to handle thing.
You mean http://wikitech.wikimedia.org/view/How_to_deploy_code? :)
I wrote that yesterday, it's still incomplete but it's a very good start.
Years ago, it was: - make sure you have someone to back your *** - edit a global setting file on Zwinger
Now fenari, zwinger's been decommissioned.
- lint it - verify your change on test.wikipedia.org (or something like that) - ask all Apaches servers to copy the new file through NFS (scap?)
sync-file for single files, scap for larger things
- verify the change in production and get ready to revert - stay around in IRC, specially in channels used by the project impacted - udpate bug report - proceed with next request
The two issues I had with this were: - The global setting file was not under a version control system which made it hard to track changes and revert mines
It is now, with an autocommit script that automatically commits changed files that haven't been touched in 30 mins.
- Making sure I will not produce a worldwide blank page (it happened once and I can tell you it gives you a huge boost of adrenaline).
Yeah there's always that. Breaking the site is easy and you have to be prepared to fix it in a hurry.
If the process is still roughly the same
Mostly, yes. The differences should be apparent from my wikitech page (and from the two redlinked from there that I have yet to write).
and that I am still allowed to connect to the server
No idea.
Roan Kattouw (Catrope)