Release manager guide is too vague about how to update docs.parrot.org #170

Closed
leto opened this Issue Oct 19, 2011 · 3 comments

Projects

None yet

3 participants

@leto
Member
leto commented Oct 19, 2011

Where is the webroot?

  1. Update http://docs.parrot.org. Run "make html" in a release copy of Parrot, and save the resources/ and html/ directories created in docs/.
    Use SSH to login to @parrot.org and expand these into a release directory (e.g. 3.8.0) in the webroot for http://docs.parrot.org.
    In "/parrot", there are symbolic links for "latest", "supported", and "devel". Update the "latest" symlink to point to your new
    directory. If this is a supported release, also update the "supported" symlink. Do not delete any old copies of the docs and don't update the
    other symlinks.
@coke
Contributor
coke commented Oct 19, 2011

Apologies, as I probably wrote that part of the docs - but I cannot ssh into docs.parrot.org at the moment, so I cannot answer the question. If you look in my home directory there, there's probably a symlink that will help you out.

@ayardley
Member

As soon as osuosl.org grants me ssh access into docs.parrot.org, I will check on this and update the release_manager_guide.

@ayardley ayardley was assigned Jan 24, 2012
@ayardley ayardley added a commit that referenced this issue Jan 27, 2012
@ayardley ayardley Update doc to fix issue #170. 74a17f0
@ayardley
Member

Done.

@ayardley ayardley closed this Jan 27, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment