<<<<<<< HEAD
=======
f4ea032adfbc27c74c02e8d90dfbacb4119575e7
git clone git@github.com:klpdotorg/ilp.git
pip install virtualenvwrapper
Add these lines to your .bashrc and source it
# add virtualenv wrappers
export WORKON_HOME=$HOME/.virtualenvs
export PROJECT_HOME=$HOME/Devel
source /usr/local/bin/virtualenvwrapper.sh
Finally source .bashrc using the following command
source ~/.bashrc
Create and activate the virtualenv
mkvirtualenv --python=/usr/local/bin/python3 ilp
workon ilp
pip install -r requirements/base.txt
createuser klp --superuser
User klp is needed to make the migrations work. Otherwise, there will be a FATAL error referencing the klp role. It needs to be superuser so that the copy command works.
The default peer authentication might not work if you're accessing the db as another user. So either set an md5
password authentication system or trust
all local connections.
emacs -nw /etc/postgresql/9.3/main/pg_hba.conf
Edit:
local all all peer
To:
local all all trust
sudo apt-get install postgresql-9.3
sudo apt-get install postgresql-9.3-postgis-2.1
Make sure the postgres application is running.
sudo -u postgres createdb -E UTF8 -O klp -T template0 ilpproduction
psql -d ilpproduction -c "CREATE EXTENSION postgis;"
mv ilp/settings/local_settings.py.sample ilp/settings/local_settings.py
OR
mv ilp/settings/prod_settings.py.sample ilp/settings/prod_settings.py
Install Postgres 9.3 or above. Have the following configuration in your local_settings.py file.
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql_psycopg2',
'NAME': 'your_db_name',
'USER': 'your_db_username',
'PASSWORD': 'your_db_password',
'HOST': '',
'PORT': '',
}
}
Run:
python manage.py migrate
python manage.py loaddata apps/*/fixtures/*.json
Databases required before beginning imports : (Get dumps from S3 server)
Once the DBs are set up, go to the imports directory and run populateILP.sh (It asssumes the db names are as specified above)
python manage.py runserver
Visit http://127.0.0.1:8000/
See PEP8 @ https://www.python.org/dev/peps/pep-0008/
ILP has two main branches:
* master
* nextrelease
These two branches are exclusively used for feature releases. Developers should create new branches while developing new features. Once the feature is ready for a "dev release", the branch can be merged to nextrelease.
And when the feature is ready to be tested by users, it can merged to the master, which gets auto-deployed to staging.
Emergeny bug fixes can be pushed to master directly without creating any branches
========================= End of document