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

3.7.1 www =1 3.7.1Version of this port present on the latest quarterly branch.

Maintainer: xenophon+fbsdports@irtnog.org

Port Added: 2012-02-07 04:58:41

Last Update: 2020-04-19 10:15:56

SVN Revision: 532093

People watching this port, also watch: py27-pymc, otrs, links, mupdf, py37-django

Also Listed In: python

License: BSD3CLAUSE

Description:

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. WWW: http://django-cms.org/

SVNWeb : Homepage

There is no configure plist information for this port.

Dependency lines:

• ${PYTHON_PKGNAMEPREFIX}django-cms>0:www/py-django-cms

To install the port: cd /usr/ports/www/py-django-cms/ && make install clean

To add the package: pkg install py37-django-cms

PKGNAME: py37-django-cms

Package flavors (<flavor>: <package>)

• py37: py37-django-cms

distinfo:

TIMESTAMP = 1585984230 SHA256 (django-cms-3.7.1.tar.gz) = 05ea915d490562413428e04acb9ecae604c63b8dc5ed9250d0e9437b1314c996 SIZE (django-cms-3.7.1.tar.gz) = 4770008

Dependencies

NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.

Build dependencies:

1. py37-setuptools>0 : devel/py-setuptools@py37
2. python3.7 : lang/python37

Runtime dependencies:

1. py37-django22>=1.11<3.0 : www/py-django22@py37
2. py37-djangocms-admin-style>=1.2 : www/py-djangocms-admin-style@py37
3. py37-django-classy-tags>=0.7.2 : www/py-django-classy-tags@py37
4. py37-django-formtools>=2.1 : www/py-django-formtools@py37
5. py37-django-sekizai>=0.7 : www/py-django-sekizai@py37
6. py37-django-treebeard>=4.3 : www/py-django-treebeard@py37
7. py37-sqlite3>0 : databases/py-sqlite3@py37
8. py37-setuptools>0 : devel/py-setuptools@py37
9. python3.7 : lang/python37

There are no ports dependent upon this port

Configuration Options

===> The following configuration options are available for py37-django-cms-3.7.1: ====> Options available for the multi DATABASE: you have to choose at least one of them MYSQL=off: MySQL database support PGSQL=off: PostgreSQL database support SQLITE=on: SQLite database support ===> Use 'make config' to modify these settings

USES:

python:3.5+

pkg-message:

If installing:

IMPORTANT / If you're upgrading from a older version of py-django-cms please read the upgrade instructions at: http://docs.django-cms.org/en/latest/upgrade/index.html The described steps further down are a distilled version of "How to install django CMS by hand" which is available at: http://docs.django-cms.org/en/latest/how_to/install.html 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: http://docs.django-cms.org/en/latest/index.html 1. Create a new Django project $ django-admin.py startproject myproject 2. Edit settings.py --- 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 'django.contrib.sites' 'cms' 'menus' 'sekizai' 'treebeard' --- Configure the LANGUAGES and LANGUAGE_CODE, e.g.: LANGUAGES = [ ('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 'cms.middleware.user.CurrentUserMiddleware' 'cms.middleware.page.CurrentPageMiddleware' 'cms.middleware.toolbar.ToolbarMiddleware' 'cms.middleware.language.LanguageCookieMiddleware' 'django.middleware.locale.LocaleMiddleware' --- 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: CMS_TEMPLATES = [ ('home.html', 'Home page template'), ] --- Add the next lines to TEMPLATES['OPTIONS']['context_processors']: 'sekizai.context_processors.sekizai' 'cms.context_processors.cms_settings' --- 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: ['templates'] --- 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 %} <html> <head> <title>{% page_attribute "page_title" %}</title> {% render_block "css" %} </head> <body> {% cms_toolbar %} {% placeholder "content" %} {% render_block "js" %} </body> </html> --- Note: See Django's template language documentation for more on how template --- inheritance works. 3. Edit urls.py --- Edit urls.py 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'^admin/', admin.site.urls), 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 manage.py migrate 6. Create an admin superuser --- For maintenance purposes it is necessary to create a admin user: $ python manage.py createsuperuser 7. Check CMS installation --- This will check your configuration, your applications, your database and --- report on any problems: $ python manage.py 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 manage.py runserver --- The CMS can now be reached http://localhost:8000/ and the admin interface --- at http://localhost:8000/admin/

Master Sites:

1. https://files.pythonhosted.org/packages/source/d/django-cms/
2. https://pypi.org/packages/source/d/django-cms/

• 2017-11-30

  Affects: */py*

  Author: mat@FreeBSD.org

  Reason: 
    Ports using Python via USES=python are now flavored.  All the py3-* ports
    have been removed and folded into their py-* master ports.
  
    People using Poudriere 3.2+ and binary packages do not have to do anything.
  
    For other people, to build the Python 3.6 version of, for example,
    databases/py-gdbm, you need to run:
  
      # make FLAVOR=py36 install
  
  

www/py-django-cms: Update to 3.7.1

* Also assign the port to Django 2.2 because Django 1.11 is End-of-Life
  since April. [1]

* Do the same for its dependencies (including www/py-django-classy-tags [2])
  and bump PORTREVISION accordingly.

Changelog:

https://github.com/divio/django-cms/blob/3.7.1/CHANGELOG.rst

PR:		245361 [1] 245360 [2]
Approved by:	maintainer timeout (14 days) [1] [2]

Convert to UCL & cleanup pkg-message (categories w)

- Update to 3.5.2
- Switch to py-django111

PR:	228092
Submitted by:	freebsd_ports@k-worx.org
Approved by:	maintainer
Sponsored by:	iXsystems Inc.

Reduce dependency on the python2 metaport

PR:		225752
Submitted by:	Yasuhiro KIMURA

Convert Python ports to FLAVORS.

  Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the

Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.

With hat:	portmgr
Sponsored by:	Absolight

- Switch forgotten ports over to py-django18
- Fix PYTHON_PKGNAMEPREFIX

Reported by:    antoinebot

- Switch all ports to www/py-django18
- Bump PORTREVISION

Remove UNIQUENAME and LATEST_LINK.

UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.

Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.

Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)

Reviewed by:	antoine, bapt
Exp-run by:	antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D3336

Update "BSD" license in www category

www/py-django-cms: convert to USES=python

Approved by:	portmgr (blanket)

Use OPTIONS helpers, and change NOPORTDOCS reference to DOCS.

- Stage support

- Convert to PYDISTUTILS_AUTOPLIST
- Stage support
- Bump PORTREVISION

Python cleanup:
- USE_PYTHON* = 2.X -> USE_PYTHON* = 2
- USE_PYTHON* = 2.X+ -> USE_PYTHON* = yes
Reviewed by:	python (mva, rm)
Approved by:	portmgr-lurkers (mat)

Add NO_STAGE all over the place in preparation for the staging support (cat:
www)

- Update to 2.4.1 [1]
- Update pkg-message

Changes: http://docs.django-cms.org/en/2.4.0/upgrade/2.4.html

PR:		ports/178988 [1]
Submitted by:	Melvyn Sopacua <melvyn@magemana.nl>
Approved by:	culot / jpaetzel (mentors, implicit), maintainer (timeout)

- Mark BROKEN fails to build

- let user to change database backend via options (default is sqlite)
- bump PORTREVISION
- trim Makefile header while here

PR:		169248
Submitted by:	Matthew X. Economou <xenophon+freebsd at irtnog dot org>
(maintainer)
Feature safe:	yes

- update to version 2.3
- update dependency upon www/py-django-sekizai (at least 0.6.1 is needed)
- fix directories at pkg-message
- use @dirrm (not @dirrmtry) for the port's own directories
- don't try to use @dirrmtry to other ports directories

while here:
- use CHEESESHOP shortcut
- remove unnecessary MASTER_SITE_SUBDIR
- strict python version to 2.x only

PR:		169599
Submitted by:	bsam
Approved by:	maintainer timeout (6 weeks)

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.

WWW: http://django-cms.org/

PR:             ports/164624
Submitted by:   Matthew X. Economou <xenophon+fbsdports@irtnog.org>

13 vulnerabilities affecting 106 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2020-08-12 14:32:19