Setting up a Lino contributor environment¶
We assume you have already Installing a Lino developer environment and that you decided to extend your developer environment into a contributor environment. As a contributor you have a local clone of the Lino code repositories because you are going to do local modifications and submit pull requests.
Run getlino to clone Lino repositories¶
getlino with the following options:
$ getlino configure --clone --devtools --redis
For details see the documentation about getlino.
Note that getlino uses the configuration values you specified during Installing a Lino developer environment.
Try one of the demo projects:
$ cd ~/lino/env/repositories/book/lino_book/projects/team $ python manage.py prep $ python manage.py runserver
Point your browser to http://localhost:8000
prep is needed only once per demo project in order to create
Running your first Lino site¶
$ cd ~/repositories/book/lino_book/projects/min1 $ python manage.py prep $ python manage.py runserver
Sign in and play around.
Create some persons and organizations. Don't enter lots of data because we are going to throw it away soon.
Set up a simulated production server¶
For testing nginx-specific issues you might want to run a "simulated" production
server that unlike a real production server uses your local repositories but
otherwise runs as a series of real nginx and wsgi and
Set shared permissions in your default virtualenv:
$ sudo chown root:www-data . $ sudo chmod g+ws .
Otherwise it might happen that nginx compiles a
.pyc file that you
cannot modify afterwards.
$ sudo env PATH=$PATH getlino configure $ sudo env PATH=$PATH getlino startsite noi first
Point your browser to http://first.localhost
When using nginx and you want to restart it, you must restart supervisor (not nginx) because the wsgi process of the site is running there. nginx itself usually doesn't need to be restarted.