|
|
(27 intermediate revisions by 5 users not shown) |
Line 1: |
Line 1: |
| {{header|websites}} | | {{header|websites}} |
| + | This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/fedorawebsites.rst |
| | | |
− | == Preparing the website for a release ==
| + | For changes, questions or comments, please contact anyone in the Fedora Infrastructure team. |
| | | |
− | === Update gpg key ===
| |
| | | |
− | As the release approaches, watch the <code>fedora-release</code> package for a
| |
− | new key to be added. Use the <code>update-gpg-keys</code> script in the
| |
− | fedora-web git repository to add it to <code>static/</code>. Manually add it
| |
− | to <code>/keys</code> and <code>/verify</code>.
| |
− |
| |
− | === Branch master for stable release in fedora-web git repository ===
| |
− |
| |
− | {{admon/note | Perhaps this should be done right after release?}}
| |
− |
| |
− | <pre>git branch f12 master && git push origin f12</pre>
| |
− |
| |
− | === Unfreeze website ===
| |
− |
| |
− | Comment out the git checkout line in
| |
− | <code>modules/fedora-web/files/syncStatic.sh</code> on <code>puppet1</code>.
| |
− |
| |
− | === Prepare puppet commits ===
| |
− |
| |
− | Prior to release day, prepare puppet commits to move the fedora-web branch to
| |
− | the release (alpha, beta, final, whatever) and, edit
| |
− | <code>redirects.conf</code> (in <code>modules/fedora-web/files</code> on
| |
− | <code>puppet1</code>) to do the right thing with <code>/get-prerelease</code>
| |
− | requests.
| |
− |
| |
− | === Fire in the hole ===
| |
− |
| |
− | On release day, wait for rel-eng to say go, then push the puppet changes
| |
− | (e.g.: <code>cd ~/puppet && git push</code>). Then, on <code>puppet1</code>
| |
− | run:
| |
− |
| |
− | <pre>
| |
− | # Ensure you have the puppet repo checked out to ~/puppet and up to date
| |
− | cd ~/puppet && make HOSTS="puppet1 proxy1 proxy2 proxy3 proxy4 proxy5" push
| |
− |
| |
− | # Once /usr/local/bin/syncStatic is updated with your changes, run
| |
− | sudo /usr/local/bin/syncStatic
| |
− |
| |
− | # To sync the changes out, you can use func if you have sudo on puppet1.
| |
− | # Otherwise, SSH to the proxies and call the below command.
| |
− | sudo func proxy\* call command run "/usr/local/bin/syncFiles.sh fedoraproject.org /srv/web/fedoraproject.org/"
| |
− | </pre>
| |
− |
| |
− | to push the updated website live.
| |
− |
| |
− | == Fedora 12 Notes ==
| |
− | (Still needs to be wikified)
| |
− |
| |
− |
| |
− | <pre>
| |
− |
| |
− | The times below are based on the timing of the website build and sync cronjobs.
| |
− | It'd be a good idea to double check those in advance.
| |
− |
| |
− | Unfreeze website (modules/fedora-web/files/syncStatic.sh), push after 9:05 AM EDT.
| |
− |
| |
− | Run sudo /usr/local/bin/syncStatic on puppet1 after 9:45 AM EDT, make sure this
| |
− | succeeds by checking /var/lib/puppet/application/fedoraproject.org.
| |
− |
| |
− | Release:
| |
− |
| |
− | Push commit to redirect get-prerelease to get-fedora.
| |
− |
| |
− | sudo func proxy\* call command run "/usr/local/bin/syncFiles.sh fedoraproject.org /srv/web/fedoraproject.org/"
| |
− |
| |
− | Manually run
| |
− |
| |
− | sudo /usr/local/bin/syncFiles.sh fedoraproject.org /srv/web/fedoraproject.org/
| |
− |
| |
− | on any proxy server where the func call did not succeed.
| |
− |
| |
− | If necessary, clear proxy caches using
| |
− |
| |
− | rm -rf /srv/cache/mod_cache/*
| |
− |
| |
− | After the site is out, do link checking and push any last-minute fixes/changes
| |
− | by committing to the git repo, running syncStatic, and syncing to the proxies
| |
− | as above.
| |
− |
| |
− | Update the static banner on start.fedoraproject.org. The procedure is the
| |
− | same as with fedoraproject.org, except that the command to run on the
| |
− | proxies is
| |
− |
| |
− | sudo /usr/local/bin/syncFiles.sh start.fedoraproject.org /srv/web/start.fedoraproject.org/
| |
− |
| |
− | Adding
| |
− |
| |
− | add release banner countdown
| |
− | add new release checksum files
| |
− | add gpg keys
| |
− |
| |
− | Watch the webmaster@ moderator queue for reports of website issues.
| |
− |
| |
− | </pre>
| |
− |
| |
− | [[Category:Websites]]
| |
| [[Category:Infrastructure SOPs]] | | [[Category:Infrastructure SOPs]] |