How does Worg publish itself as a website?
The server behind https://orgmode.org website takes care of publishing
How long does it take for a change to be published?
The changes should be available immediately following your
There is a problem. Can I check the export output?
As soon as you push a commit to the worg git repository on the org server, the publishing process is triggered. You should see the output of the publishing process in your terminal. If there's a problem, you should see the error in this output.
Looks like file XXX breaks the export. What can I do?
- Put this file in the FIXME directory at the root of the Worg repository. Files in this FIXME directory won't be published.
- Fix the page or contact the author of the page telling him about the problem.
Where are the "raw" .org files kept?
In addition to publishing the html versions of the .org files Worg's git repository, the raw source .org files are also put in https://orgmode.org/worg/sources. It is nice to make the .org file available for those following a tutorial so that the actual .org file is viewable in addition to reading through the online html version. To do this, simply link to the file in the worg sources directory:
- If the page in the git repository is
- Link like so:
Are there any writing conventions?
Please don't use file variables in your org files.
Can Worg execute code (via Babel)?
No. The default automated export does not allow code execution on the server for obvious security reasons.
What software is available on Worg for Babel code execution?
If babel code execution works on your machine, it doesn't mean it will work on the orgmode.org server. Here is the list of available software on orgmode.org:
What .emacs.el file is used on the server?
I want it for my own server!
Here is the detailed recipe:
- Configure your
~/.emacs.elto know about your publishing projects (more information on publishing here and here).
(setq org-export-htmlize-output-type 'css)in
C-h v org-export-htmlize-output-typefor more information about this. Also
C-h v org-export-htmlize-generate-cssmight help.)
~/bin/pull-worg.shcontaining this script:
#!/bin/bash # unless this is already done elsewhere: export PATH=$PATH:/home/you/bin/ # go to the place where you pull Worg cd /home/you/git/worg/; # pull worg /home/you/bin/git-pull
~/bin/publish-worg.shcontaining this script:
#!/bin/bash # Adapt it to point at your emacs executable /home/you/bin/emacs23 --batch -l ~/.emacs.el -f org-publish-all
Cron the two scripts to run every hour, not at the same time
0 * * * * /home/you/bin/pull-worg.sh >> /dev/null 2>&1 30 * * * * /home/you/bin/publish-worg.sh >> /dev/null 2>&1
- Sit and do something else while your Org repository is automagically exported to HTML