2011-08-31 01:05:23 +00:00
|
|
|
regluit
|
2011-08-31 03:46:55 +00:00
|
|
|
=======
|
|
|
|
|
|
|
|
A 'monolithic' alternative to [unglu](http://github.com/gluejar/unglu)
|
2011-08-31 03:53:25 +00:00
|
|
|
for the unglue.it website. regluit essentially on Django project that contains
|
2011-08-31 03:53:02 +00:00
|
|
|
three applications: `frontend`, `api` and `core` that can be deployed and
|
|
|
|
configured to as many instances that are needed to support traffic. The key
|
|
|
|
difference with [unglue](http://github.com/gluejar/unglu) is that the
|
|
|
|
`frontend` app is able to access database models from `core` in the same
|
|
|
|
way that the `api` is able to. Which should simplify some things.
|
2011-08-31 03:46:55 +00:00
|
|
|
|
|
|
|
Develop
|
2011-08-31 01:05:23 +00:00
|
|
|
-------
|
2011-08-31 03:46:55 +00:00
|
|
|
|
|
|
|
Here are some instructions for setting up regluit for development on
|
|
|
|
an Ubuntu system:
|
|
|
|
|
|
|
|
1. `aptitude install python-setuptools`
|
|
|
|
1. `sudo easy_install virtualenv virtualenvwrapper`
|
|
|
|
1. `git clone git@github.com:Gluejar/regluit.git`
|
|
|
|
1. `cd reglueit`
|
|
|
|
1. `mkvirtualenv --no-site-packages regluit`
|
|
|
|
1. `pip install -r requirements.pip`
|
|
|
|
1. `add2virtualenv ..`
|
|
|
|
1. `echo 'export DJANGO_SETTINGS_MODULE=regluit.settings.dev' >> ~/.virtualenvs/regluit/bin/postactivate`
|
|
|
|
1. `deactivate ; workon regluit`
|
|
|
|
1. `django-admin.py syncdb --migrate`
|
|
|
|
1. `django-admin runserver`
|
2011-08-31 03:48:17 +00:00
|
|
|
1. point your browser at http://localhost:8000/
|
|
|
|
|