Manage Content with Markdown and Mango on Debian 5 (Lenny)

Select distribution:
Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Deprecated

This guide has been deprecated and is no longer being maintained.

Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

Mango is a simple static content management system for publishing blogs from content stored in plain text files. Built as a dynamic web application using components from the Django framework, Mango is simple to deploy and administer and uses the Markdown lightweight markup language to process text. This guide describes the process for configuring a Mango-based site using the Apache HTTP Server and mod_wsgi to handle the dynamic aspects of the website.

Set the Hostname

Before you begin installing and configuring the components described in this guide, please make sure you’ve followed our instructions for setting your hostname. Issue the following commands to make sure it is set properly:

hostname
hostname -f

The first command should show your short hostname, and the second should show your fully qualified domain name (FQDN).

Prepare System

Issue the following commands to update your system’s package database, ensure that all installed applications are up to date, and install all dependencies required for running Mango:

apt-get update
apt-get upgrade
apt-get install apache2 python-setuptools libapache2-mod-wsgi build-essential mercurial python-dev libxml2-dev libxslt-dev zlib1g-dev
easy_install pip

This guide describes the process for installing the Mango CMS on the root level of the example.com, with the DocumentRoot of /srv/www/example.com/public_html. Throughout this guide, replace these paths and domains in examples with the actual paths of your site.

Install Mango

Issue the following command to create the required directories for the Mango VirtualHost:

mkdir -p /srv/www/example.com/public_html
mkdir -p /srv/www/example.com/logs

Issue the following commands to install Django, create a Django project in the application directory, download the Mango application, install required Python modules, and prepare files and file permissions for Mango:

cd /srv/www/example.com/
pip install Django
django-admin.py startproject application
cd /srv/www/example.com/application
hg clone http://bitbucket.org/davidchambers/mango
pip install -r /srv/www/example.com/application/mango/requirements.txt
mkdir /srv/www/example.com/application/content
touch /srv/www/example.com/application/mango/mango.log
chown www-data:www-data /srv/www/example.com/application/mango/mango.log

Edit the INSTALLED_APPS list at the end of the /srv/www/example.com/application/settings.py file to resemble the following:

File: /srv/www/example.com/application/settings.py
1
2
3
INSTALLED_APPS = (
    'mango',
)

Edit the ROOT_URLCONF variable in the /srv/www/example.com/application/settings.py file to resemble the following:

File: /srv/www/example.com/application/settings.py
1
ROOT_URLCONF = 'mango.urls'

Edit the urlpatterns array in the /srv/www/example.com/application/urls.py file to resemble the following:

File: /srv/www/example.com/application/urls.py
1
2
3
urlpatterns = patterns('',
    (r'', include('mango.urls')),
)

Create a application.wsgi file, using the following as a model:

File: /srv/www/example.com/application/application.wsgi
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
import os
import sys

path = '/srv/www/example.com'
if path not in sys.path:
    sys.path.append(path)
    sys.path.append(path + '/application')
    sys.path.append(path + '/application/mango')

sys.path.append('/srv/www/example.com/application')

os.environ['PYTHON_EGG_CACHE'] = '/srv/www/example.com/.python-egg'

os.environ['DJANGO_SETTINGS_MODULE'] = 'settings'

import django.core.handlers.wsgi
application = django.core.handlers.wsgi.WSGIHandler()

Configure Apache

Create a VirtualHost specification based on the following example:

File: /etc/apache2/sites-available/example.com
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
<VirtualHost *:80>
   ServerName example.com
   ServerAlias www.example.com
   ServerAdmin username@example.com

   DocumentRoot /srv/www/example.com/public_html

   ErrorLog /srv/www/example.com/logs/error.log
   CustomLog /srv/www/example.com/logs/access.log combined

   WSGIScriptAlias / /srv/www/example.com/application/application.wsgi

   Alias /static /srv/www/example.com/application/mango/static
</VirtualHost>

Issue the following command to enable the “VirtualHost and restart the web server to load the configuration:

a2ensite example.com
/etc/init.d/apache2 restart

You will need to restart the server anytime you make changes to the Apache configuration or application.wsgi files.

Configure the Mango Site

The behavior of the Mango application is controlled the settings in the /srv/www/example.com/application/mango/settings/default.py file which you can override in a /srv/www/example.com/application/mango/settings/custom.py file. Add configuration values to custom.py as needed to produce your site. The most relevant settings are below:

File: /srv/www/example.com/application/mango/settings/custom.py
1
2
3
DOCUMENTS_PATH = 'content'

SITE_TITLE = 'example Blog'

The paths specified in this file are relative to the top level of the Django application, for this document: /srv/www/example.com/application/. In the above example, all documents processed by Mango are stored in the /srv/www/example.com/application/docs/ directory. Explore each setting in this document while you configure your site.

Write Content with Mango

All content with Mango exists in source as Markdown, a lightweight markup language that mirrors formatting conventions for plain text emails. Markdown is designed to be easy to read and write, and can be translated efficiently into high quality HTML. Consider the following example entry:

File: /srv/www/example.com/application/docs/first-post.text
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
date: 02 February 2011
time: 08:06am
tags: blog, meta, example

#### First Post

Welcome to Mango. If this page appears in full HTML glory (with **bold** and _emphasized_ text) then everything's probably working correctly. **Congratulations!**

## More Details

Learn more about [Markdown][]!

[Markdown]:<http://daringfireball.net/projects/markdown/>

The first three lines of this file define header values that are processed by the Markdown implementation and used to control how Mango displays and organizes the posts. The format of the date and time fields is very strict, adhere to the format above. You may now visit your site at http://example.com/. To add new posts to your site, simply save files using the above format in the content/ directory.

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

This page was originally published on


Your Feedback Is Important

Let us know if this guide was helpful to you.


Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.