py36-django-cms - Content management system built with the Django framework

Property Value
Distribution FreeBSD 12
Repository FreeBSD Ports Latest amd64
Package filename py36-django-cms-3.5.2.txz
Package name py36-django-cms
Package version 3.5.2
Package release -
Package architecture amd64
Package type txz
Category python www
Download size 1.57 MB
Installed size 12.66 MB
A free and open source content management system for publishing
content on the World Wide Web and intranets.  It is based on Django
and written in Python.
- MYSQL: off
- PGSQL: off
- SQLITE: on
If you're upgrading from a older version of py-django-cms please read the
upgrade instructions at:
The described steps further down are a distilled version of "How to install
django CMS by hand" which is available at:
The manual gives enough information how to setup py-django-cms for
development use. For production environments please consider to read the
full documentation available at:
1. Create a new Django project
$ startproject myproject
2. Edit
--- Set a SITE_ID by adding the following line:
SITE_ID = 1	# 1 will suffice in most cases
--- Add the next lines to INSTALLED_APPS:
'djangocms_admin_style' 	# must come BEFORE django.contrib.admin
--- Configure the LANGUAGES and LANGUAGE_CODE, e.g.:
('en', 'English'),
('de', 'German'),
LANGUAGE_CODE = 'en'	# For simplicity's sake at this stage it is worth
# changing the default en-us in that you'll find in
# the LANGUAGE_CODE setting to en.
--- Add the following lines to MIDDLEWARE_CLASSES:
'cms.middleware.utils.ApphookReloadMiddleware'	# Optional, but useful
--- Add MEDIA_URL (where media files will be served) and MEDIA_ROOT (where they
--- will be stored):
MEDIA_URL = "/media/"
MEDIA_ROOT = os.path.join(BASE_DIR, "media")
--- See the Django documentation for guidance on serving media files in
--- production.
--- Add a CMS_TEMPLATES section that will be the project's default template:
('home.html', 'Home page template'),
--- Add the next lines to TEMPLATES['OPTIONS']['context_processors']:
--- Django needs to be know where to look for its templates, so add following
--- line (the appropriate directory will be created in the next step) to the
----TEMPLATES['DIRS'] list:
--- In the root of the project, create a templates directory, and in that,
--- home.html, a minimal django CMS template:
{% load cms_tags sekizai_tags %}
<title>{% page_attribute "page_title" %}</title>
{% render_block "css" %}
{% cms_toolbar %}
{% placeholder "content" %}
{% render_block "js" %}
--- Note: See Django's template language documentation for more on how template
--- inheritance works.
3. Edit
--- Edit and add url(r'^', include('cms.urls')) to the urlpatterns
--- list. It should come after other patterns, so that specific URLs for other
--- applications can be detected first.
--- You'll also need to have an import for django.conf.urls.include and
--- configure a media file serving for development purposes:
from django.conf import settings
from django.conf.urls import url, include
from django.conf.urls.static import static
urlpatterns = [
url(r'^', include('cms.urls')),
] + static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)
4. Setup the relational database backend
--- For testing purpose SQLite can be used and it is configured by default
--- in a new Django project's DATABASES.
--- Refer to Django's DATABASES setting documentation for the appropriate
--- configuration when PostgreSQL or MySQL are used as database backends.
5. Run migrations to create database tables
--- When a database backend has been choosen and set up properly, run the
--- following command:
$ python migrate
6. Create an admin superuser
--- For maintenance purposes it is necessary to create a admin user:
$ python createsuperuser
7. Check CMS installation
--- This will check your configuration, your applications, your database and
--- report on any problems:
$ python cms check
--- When there are no errors continue with the last step.
8. Start the CMS
--- The django CMS project will now run by issuing:
$ python runserver
--- The CMS can now be reached http://localhost:8000/ and the admin interface
--- at http://localhost:8000/admin/


Package Version Architecture Repository
py36-django-cms-3.5.2.txz 3.5.2 i386 FreeBSD Ports Quarterly
py36-django-cms-3.5.2.txz 3.5.2 amd64 FreeBSD Ports Quarterly
py36-django-cms-3.5.2.txz 3.5.2 i386 FreeBSD Ports Latest
py36-django-cms - - -


Name Value
py36-django-classy-tags = 0.8.0_1
py36-django-formtools = 2.1
py36-django-sekizai = 0.10.0
py36-django-treebeard = 4.3
py36-django111 = 1.11.20
py36-djangocms-admin-style = 1.2.8
py36-setuptools = 41.0.0
py36-sqlite3 = 3.6.8_7
python36 = 3.6.8_2


Type URL
Binary Package py36-django-cms-3.5.2.txz
Source Package www/py-django-cms

Install Howto

Install py36-django-cms txz package:

# pkg install py36-django-cms

See Also

Package Description
py36-django-common-helpers-0.9.2.txz Common things every Django app needs
py36-django-configurations-2.1_1.txz Django project configuration using the composability of Python classes
py36-django-constance-2.4.0.txz Dynamic Django settings
py36-django-contact-form-1.7.txz Generic contact-form application for Django
py36-django-context-decorator-1.5.0.txz Remove the need to call super().get_context_data(**kwargs) in nearly every view
py36-django-contrib-comments-1.9.1.txz Code formerly known as django.contrib.comments
py36-django-cors-headers-3.1.1.txz Handles server headers required for Cross-Origin Resource Sharing
py36-django-countries-5.3.txz Provides country choices for use with django
py36-django-crispy-forms-1.8.1.txz Best way to have Django DRY forms
py36-django-cron-0.5.1.txz Running Python crons in a Django project
py36-django-datetime-widget-0.9.3_1.txz Simple and clean widget for DateTimeField
py36-django-dpaste-3.3.1.txz Django based pastebin for text and code
py36-django-easy-thumbnails-2.5.txz Easy thumbnails for Django
py36-django-extensions-2.1.7.txz Global custom management extensions for the Django Framework
py36-django-filer-1.3.2.txz File and Image Management Application for django