56
58
Installing from a Debian package
57
59
================================
59
64
Installing from source
60
65
======================
62
.. If this list changes, you also need to change the list above.
67
When setting up a development IVLE environment on Ubuntu 9.04 or later,
68
there are scripts to automate most of the process. First get and extract
69
a release, or check out the latest code from the bzr branch: ::
73
This will create a new directory, ``ivle``, containing a pristine
74
source tree. The remaining steps assume that you are in this new
77
The ``ivle-dev-setup`` script will configure PostgreSQL, Apache, IVLE
78
and the filesystem to cooperate, getting you most of the way to a
79
working system in just one step: ::
84
This reconfigures parts of your system, and has the potential to
85
break other applications using Apache or PostgreSQL. It may also
86
fail to execute if you have existing incompatible configurations
90
This may take a few minutes, and will ask you to confirm installation
91
of the dependency packages.
93
Upon completion, you must build a self-contained jail in which to run
94
untrusted user code. ``ivle-dev-setup`` will have configured most of
95
the necessary settings, but you may wish to use a local Ubuntu mirror
96
to improve speed or minimise download costs. If you don't wish to use
97
a special mirror, you may omit the first step. ::
99
sudo ivle-config --jail/mirror http://url.to.mirror/ubuntu
100
sudo ivle-buildjail -r
103
``ivle-buildjail`` will download a large volume of package data --
104
potentially some hundreds of megabytes.
106
``ivle-buildjail`` will download, unpack and install a minimal Ubuntu
107
system and configure it for IVLE usage. This could take a while.
109
Once the jail has been successfully built, IVLE is up and running,
110
but with no user accounts or other data in place. For development
111
or demonstration purposes, sample data (including fictitious users,
112
subjects, and projects) can be loaded.
114
For other environments, it may be more appropriate to start with an
115
empty database and just create users as required.
117
To load the sample data: ::
119
sudo ivle-loadsampledata examples/db/sample.sql
122
If you answer 'yes' to the ``ivle-loadsampledata`` prompt, any
123
existing data in your IVLE database will be **permanently
126
... or to add a new admin user: ::
128
sudo ivle-adduser --admin -p password username 'Full Name'
130
You should then be able to browse to http://ivle.localhost/, and
131
log in with username ``admin`` and password ``password``, or the
132
username and password that you gave to ``ivle-adduser``.
138
If the automatic installation scripts do not work, or if you want more
139
control over the whole process, these manual steps are probably for
140
you. But you need not read this section at all if you were able to log
141
in after following the steps above.
143
.. If this list changes, you also need to change the list above, and
144
the command in bin/ivle-dev-setup.
64
146
If you want to grab all of the required packages in one command, use::
66
148
sudo apt-get install apache2 libapache2-mod-python libapache2-svn \
67
149
python2.6 python-cjson python-configobj python-docutils python-epydoc \
68
python-formencode python-genshi python-psycopg2 python-svn python-routes \
69
python-storm libjs-jquery postgresql subversion debootstrap rsync \
150
python-formencode python-genshi python-psycopg2 python-svn python-storm \
151
libjs-jquery postgresql subversion debootstrap rsync build-essential
72
153
While installing from a distribution package is often a better idea for
73
154
users, developers will need to install from a plain source tree.
added
removed
doc/man/install.rst
