@@ -45,11 +45,6 @@ Update pip inside the virtual environment
45
45
Use the django CMS installer
46
46
============================
47
47
48
- .. note ::
49
-
50
- The django CMS Installer is not yet available for django CMS 3.6 or Django 2 or later.
51
-
52
- This section will be updated or removed before the final release of django CMS 3.6.
53
48
54
49
The `django CMS installer <https://github.com/nephila/djangocms-installer >`_ is
55
50
a helpful script that takes care of setting up a new project.
@@ -67,25 +62,16 @@ Create a new directory to work in, and ``cd`` into it::
67
62
68
63
Run it to create a new Django project called ``mysite ``::
69
64
70
- djangocms -f -p . mysite
65
+ djangocms mysite
71
66
72
67
This means:
73
68
74
69
* run the django CMS installer
75
- * install Django Filer too (``-f ``) - **required for this tutorial **
76
- * use the current directory as the parent of the new project directory (``-p . ``)
77
70
* call the new project directory ``mysite ``
78
71
79
- .. note :: **About Django Filer**
80
-
81
- Django Filer, a useful application for managing files and processing images. Although it's not
82
- required for django CMS itself, a vast number of django CMS addons use it, and nearly all django
83
- CMS projects have it installed. If you know you won't need it, omit the flag. See the `django
84
- CMS installer documentation for more information <https://djangocms-installer.readthedocs.io> `_.
85
-
86
72
87
73
.. warning ::
88
- djangocms-installer expects directory `` . `` to be empty at this stage, and will check for this,
74
+ djangocms-installer expects current directory to be empty at this stage, and will check for this,
89
75
and will warn if it's not. You can get it to skip the check and go ahead anyway using the ``-s ``
90
76
flag; **note that this may overwrite existing files **.
91
77
0 commit comments