Differences between revisions 1 and 2
Revision 1 as of 2008-05-12 13:01:00
Size: 1355
Comment:
Revision 2 as of 2008-05-12 13:12:39
Size: 2943
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
* config.ini : for planet.python.org
* jython.ini : for planet.jython.org
 * config.ini : for planet.python.org
 * jython.ini : for planet.jython.org
Line 26: Line 26:
(run.sh is a little wrapper script; it can be useful to execute "run.sh -o <config-file>"
when experimenting with template changes.)
Line 28: Line 31:
The mechanical task of adding and removing feeds is pretty easy: edit the appropriate config.
changes.
Line 29: Line 34:
Add/drop requests are currently sent to webmaster; maybe we should set up a new alias for Planet-related requests.
Line 30: Line 36:
Editorially speaking: the feed list started out as 'feeds from members of the Python community',
and there wasn't much concern about whether they were posting Python-related content or not. As the list of feeds grew longer, I started to want to reduce the number of posts, and began choosing to use Python-specific category feeds when they're available.

However, I don't get upset over non-Python related posts as long as the weblog in
question still posts Python-related content fairly often. (I haven't defined a bright-line test for
what 'fairly often' means.) Occasionally I'll see weblog comments that ask the
author 'why is this political/personal stuff showing up on Planet Python?'; these sorts of comments make me sad, but I can't think of a good way to tell these commenters to just deal with it.
 
In the past I have dropped feeds of people who began writing exclusively about non-Python topics, sometimes
after sending them an e-mail asking if this is a temporary or permanent change (sometimes it's obvious).
Generally I'll drop feeds that haven't been updated at all in 9 months, but I haven't done a systematic liveness check in at least a year.
Line 33: Line 50:
* Possible task: move entire set-up to ximinez.python.org, which runs more of the dynamic content for *.python.org.  * Possible task: move entire set-up to ximinez.python.org, which runs more of the dynamic content for *.python.org.
Line 35: Line 52:
* Move set-up to  * Update code to latest Planet''''''Planet or Venus release.

planet.python.org setup

planet.python.org is currently hosted on dinsdale.python.org. It's running a 2005 version of the software

The set-up is in the /data/planet/ directory. Templates and the configuration files are in /data/planet/config/. Currently the configuration files are:

  • config.ini : for planet.python.org
  • jython.ini : for planet.jython.org

The Subversion URL for the repository is file:///data/repos/systems/dinsdale/data/planet/code/ on dinsdale, or svn+ssh://svn.python.org/data/repos/systems/ for remote access.

Currently the live Planet set-up is under my user ID on dinsdale; we should move it to some generic user ID and put it in some common group. There's no commit hook that automatically updates the live files after a checkin; instead I just log into dinsdale, edit config.ini or jython.ini as desired, commit it, and wait for the next scheduled update to run.

The sites are updated with the following cron jobs (again, under my user ID):

37 1,4,7,10,13,16,19,21 * * * /data/planet/run.sh /data/planet/config/config.ini
47 1,10,19 * * * /data/planet/run.sh /data/planet/config/jython.ini

(run.sh is a little wrapper script; it can be useful to execute "run.sh -o <config-file>" when experimenting with template changes.)

Adding/removing feeds

The mechanical task of adding and removing feeds is pretty easy: edit the appropriate config. changes.

Add/drop requests are currently sent to webmaster; maybe we should set up a new alias for Planet-related requests.

Editorially speaking: the feed list started out as 'feeds from members of the Python community', and there wasn't much concern about whether they were posting Python-related content or not. As the list of feeds grew longer, I started to want to reduce the number of posts, and began choosing to use Python-specific category feeds when they're available.

However, I don't get upset over non-Python related posts as long as the weblog in question still posts Python-related content fairly often. (I haven't defined a bright-line test for what 'fairly often' means.) Occasionally I'll see weblog comments that ask the author 'why is this political/personal stuff showing up on Planet Python?'; these sorts of comments make me sad, but I can't think of a good way to tell these commenters to just deal with it.

In the past I have dropped feeds of people who began writing exclusively about non-Python topics, sometimes after sending them an e-mail asking if this is a temporary or permanent change (sometimes it's obvious). Generally I'll drop feeds that haven't been updated at all in 9 months, but I haven't done a systematic liveness check in at least a year.

Tasks

  • Possible task: move entire set-up to ximinez.python.org, which runs more of the dynamic content for *.python.org.
  • Update code to latest PlanetPlanet or Venus release.

Admin/PlanetSetup (last edited 2015-08-12 17:32:45 by MarcAndreLemburg)

Unable to edit the page? See the FrontPage for instructions.