summaryrefslogtreecommitdiffstats
path: root/askbot/doc/source/initial-configuration.rst
blob: abef2e48e3bb70b99de2f9c269d8af4746d6d879 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
.. _compile-time-configuration:

===============================
Initial Configuration of Askbot
===============================

While most configuration settings for askbot can be done at any time :ref:`through the web-interface <run-time-configuration>`, some manipulations on the server are still necessary.


Installing Askbot as a new Django project (standalone app)
==========================================================

.. note::
    Firstly - if you are preparing the project directory manually,
    make sure that the directory name does not
    have the `.` - dot - symbol, because it is illegal for Python modules. 
    For example::

        mkdir mydjangosite
        cd mydjangosite

When installing Askbot for the first time, you will need to initialize the project setup files by typing::

    askbot-setup

and answering the questions. The `askbot-setup` script will ask you where to deploy Askbot. If you are in
the directory where the Askbot project resides, you can answer `.` (`.` refers to the current directory).
There may be an error message; ignore it.

.. note::

    All Django sites have four project-wide files::

        settings.py - the main settings configuration file
        urls.py     - main url configuration
        __init__.py - often empty but needed for Python
        manage.py   - the hook allowing to run management commands

    `askbot-setup` adds those files to the directory you select (and some more things specific to Askbot).

.. versionadded:: 0.7.24
    `askbot-setup` also have command line arguments such as folder name(name), database name, database password and database user also added verbosity support. 
    You can also specify a local settings file to append it's contents to the deployment settings file.

    +----------------------------------+------------------------------------------------------------+
    | Parameter                        | Purpose                                                    |
    +==================================+============================================================+
    | -n <NAME>                        | Name of the instance, this is the name that the            |
    |                                  | folder will use.                                           |
    +----------------------------------+------------------------------------------------------------+
    | -e <DATABASE_ENGINE>             | Integer values: 1 - postgresql, 2 - sqlite3, 3 - mysql     |
    +----------------------------------+------------------------------------------------------------+
    | -d <DATABASE_NAME>               | The database name that the instance will use.              |
    +----------------------------------+------------------------------------------------------------+
    | -u <DATABASE_USER>               | The database user that the instance will use.              |
    +----------------------------------+------------------------------------------------------------+
    | -p <DATABASE_PASSWORD>           | The database password for the user.                        |
    +----------------------------------+------------------------------------------------------------+
    | --domain=<DOMAIN_NAME>           | Domain name for the application.                           |
    +----------------------------------+------------------------------------------------------------+
    | --append-settings=<SETTINGS_FILE>| Allows to append a setting file content to the             |
    |                                  | settings file, the parameter is the file to use.           |
    +----------------------------------+------------------------------------------------------------+


.. note::

    `askbot-setup` command line arguments detail parameter is available when you type: askbot-setup --h.

Note that if you already have a Django site you will not want to use `askbot-setup`, because you don't want to just overwrite your existing settings.py. See below for instructions.

Another thing you have to do if you are creating a brand new Django project is edit the file `settings.py`_. At the very minimum, you will need to provide the correct values to some settings.

All values must be enclosed in single quotes, as shown below::

    DATABASE_ENGINE = '' #e.g. 'mysql'
    DATABASE_NAME = '' #name of the database you created, e.g. 'askbot'.
    DATABASE_USER = '' #name of the database user, e.g. 'askbotuser'.
    DATABASE_PASSWORD = '' #password to the database
    CSRF_COOKIE_DOMAIN = ''#e.g. 'example.com' or 'askbot.example.com' (localhost/IP address for tests)

.. note::

    The files settings.py_ and urls.py_ may also need to be touched up 
    when you upgrate the software, because new versions may bring 
    new dependencies and add new site urls.


Adding Askbot to an existing Django project
===========================================

If you are adding askbot to an existing Django project, you will need to
merge settings.py_ and urls.py_ into your project manually. The templates to be used can be found
in the `askbot/setup_templates` subdirectory.


.. _urls.py: http://github.com/ASKBOT/askbot-devel/blob/master/askbot/setup_templates/urls.py
.. _settings.py: http://github.com/ASKBOT/askbot-devel/blob/master/askbot/setup_templates/settings.py