Publishing to web.git (Using Publican 2)
Prerequisites
To follow this procedure, you must:
- be a member of the docs-publishers group
- have a local copy of the book checked out from the book's git or SVN repo
Preparation
- Create a local copy of the git repository of the docs.fedoraproject.org website:
git clone ssh://USERNAME@git.fedorahosted.org/git/docs/web.git
Where USERNAME is your FAS username.
Large download
This download will take some time, even on fast connections. - Change into the directory into which you downloaded the web.git repo, and make a copy of homepage.tmp named homepage.cfg:
cp homepage.tmp homepage.cfg
- Edit the homepage.cfg file to provide the absolute paths to the fedoradocs.db file and the public_html directory. For example, if you downloaded the web.git repo to the fedoradocs subdirectory of your home directory, your homepage.cfg file might look like:
# Config::Simple 4.59 # Tue May 11 13:53:03 2010 db_file: /home/jsmith/fedoradocs/web/fedoradocs.db toc_path: /home/jsmith/fedoradocs/web/public_html host: http://docs.fedoraproject.org title: "Fedora Documentation" search: '<p/>'
- Make sure you have the latest version of Publican and the Fedora brand package. As root, run:
yum update publican publican-fedora
Publishing a document
- Update your copy of the docs.fedoraproject.org website. In the directory where you keep your local copy of the site, run:
git pull
- Change to the directory where you keep a checked-out copy of the document that you want to publish, then run:
publican clean
and then runpublican build --embedtoc --publish --formats epub,html,html-single,pdf --langs LANGUAGE_CODES
where LANGUAGE_CODES is a comma-separated list of the languages in which you want to publish this document ( for example, en-US ). - Browse to the publish subdirectory and to the documents themselves inside it to ensure that the documents have built as you expected. In particular, verify:
- the product name is Fedora (note capitalization)
- the version number is correct
- the document title is properly capitalized and spaced: for example, Foo Guide, not foo-guide
- Install the book to the Fedora website:
publican install_book --site_config PATH_TO_SITE_CONFIG_FILE --lang LANGUAGE_CODE
where PATH_TO_SITE_CONFIG_FILE is the path to the homepage.cfg file in your local copy of the docs.fedoraproject.org website, and LANGUAGE_CODE is the language in which you are publishing the document. Note that you can only run publican install_book for one language at a time. - public_html/index.html has redirect logic that sends ro-RO requests to public_html/ro/index.html which does not exist, instead of public_html/ro-RO/index.html which does exist. After installing books, please check the locales variable in public_html/index.html and change ro to ro-RO if needed.
- Change to the directory in which you keep your local copy of the site and run:
git add . git commit -m "DESCRIPTION_OF_YOUR_CHANGES" git push
Removing a document
To remove a document for a particular version of Fedora in a particular language:
- Update your copy of the docs.fedoraproject.org website. In the directory where you keep your local copy of the site, run:
git pull
- Change to the directory where you keep a checked-out copy of the document that you want to remove, then run:
publican remove_book --site_config PATH_TO_SITE_CONFIG_FILE --lang LANGUAGE_CODE
where PATH_TO_SITE_CONFIG_FILE is the path to the homepage.cfg file in your local copy of the docs.fedoraproject.org website, and LANGUAGE_CODE is the language in which you are removing the document. Note that you can only run publican remove_book for one language at a time. - public_html/index.html has redirect logic that sends ro-RO requests to public_html/ro/index.html which does not exist, instead of public_html/ro-RO/index.html which does exist. After removing books, please check the locales variable in public_html/index.html and change ro to ro-RO if needed.
- Change to the directory in which you keep your local copy of the site and run:
git add . git commit -m "DESCRIPTION_OF_YOUR_CHANGES" git push
- Publican can only remove the local files and directories on your system, not their record in Git. To remove the deleted files from your local Git repo, run the following command from the directory in which you keep the local copy of the site (the same place you were to run the previous step):
for f in $(git ls-files --deleted); do git rm $f; done
Then push these changes to the remote repo:
git commit -m"rm unused files" git push
A "git rm" command gone wrong can cause widespread damage to the documentation site. If you are not absolutely sure of what you are doing, ask for help.
Updating a document
To update a document previously published in a particular language for a particular version of Fedora, change into the directory in which you keep a checked-out copy of the document, then run follow the instructions in the Publishing a document procedure to build, install, and push the book, just as if you were installing it for the first time. Publican automatically replaces the old version with the new one.
Working with a translated document
The Fedora Docs Project uses Transifex.net as the docs translation management system. Refer to Setting up a document with Transifex for instructions on how to prepare, update and publish a translated document using Publican and Transifex.net.
Publishing using Koji (Using Publican >= 4)
This is the new way of publishing Fedora documentation. This way does away with the web.git repository as used above instead using Koji as a means of managing the documentation in RPMs.
Preparation
First, the publican.cfg file must contain a line making the SRPMs that are built to be for el6:
os_ver: .el6
Next, you may have to play around with the formatting of the versions in your revision history which is now used (in Publican 4.x) as the version of the guide. In particular, in older versions of Publican, revision numbers could be a single number, such as 42. In Publican 4 and later, your revisions should also contain a release, such as 42-1.
Building the SRPM
Publican will build the SRPM very easily by issuing the following command:
publican package --lang en-US
Obviously the language switch will have to be modified for each language you wish to publish.
Pushing to Koji
To push your SRPM to Koji just issue this command:
koji build el6-docs tmp/rpm/Fedora-Security_Guide-19-web-en-US-19.1-1.el6.src.rpm
In the above example I've just pushed the F19 version of the Fedora Security Guide to Koji to be built. Once Koji builds it, the documentation server will do a yum update and install any new or updated books at that time.
Removing a document from Koji
Adding a new guide
If your guide hasn't been added to Koji (and this must be done for each Fedora version and language) then you should open a request with Fedora Release Engineering asking that the RPM name (e.g. Fedora-Security_Guide-19-web-en-US) be added to the el6-docs repo.
Publishing translations (Publican 4)
publican update_po --firstname=<firstname> --surname=<surname> --email=<email address> --langs=all publican package --lang=<lang> koji build el6-docs tmp/rpm/<SRPM>
Publishing updated translations (Publican 4)
publican add_revision --firstname=<first name> --surname=<surname> --email=<email address> --lang=<lang> --member=<An entry to be added to the revision. Can be specified multiple times.> --revnumber=<revision number> publican package --lang=<lang> koji build el6-docs tmp/rpm/<SRPM>