Testing
9da8a63dd4
We're starting to see developers use subkeys of their primary key to sign packages, which we aren't handling well in the web interface. These subkeys show up as unknown, which isn't strictly true. Start the process of being able to handle these keys by adding a model that will store all known keys and subkeys and the relationships among them, as well as which developer owns each. Signed-off-by: Dan McGee <dan@archlinux.org> |
||
---|---|---|
devel | ||
main | ||
mirrors | ||
news | ||
packages | ||
public | ||
releng | ||
retro | ||
sitestatic | ||
templates | ||
todolists | ||
visualize | ||
__init__.py | ||
.gitattributes | ||
.gitignore | ||
archweb.wsgi | ||
AUTHORS | ||
feeds.py | ||
HACKING | ||
LICENSE | ||
local_settings.py.example | ||
manage.py | ||
newrelic.ini | ||
README | ||
requirements_prod.txt | ||
requirements.txt | ||
settings.py | ||
sitemaps.py | ||
TODO | ||
urls.py |
# Archweb README To get a pretty version of this document, run $ markdown README > README.html # License See LICENSE file. # Authors See AUTHORS file. # Dependencies - python2 - python2-virtualenv # Python dependencies More detail in `requirements.txt` and `requirements_prod.txt`; it is best to use virtualenv and pip to handle these. But if you insist on (Arch Linux) packages, you will probably want the following: - django - python2-psycopg2 - python2-markdown - python2-south - python2-memcached # Testing Installation 1. Run `virtualenv2`. $ cd /path/to/archweb && virtualenv2 ./env/ 2. Activate the virtualenv. $ source ./env/bin/activate 2. Install dependencies through `pip`. (archweb-env) $ pip install -r requirements.txt 3. Copy `local_settings.py.example` to `local_settings.py` and modify. Make sure to uncomment the appropriate database section (either sqlite or PostgreSQL). 4. Sync the database to create it. (archweb-env) $ ./manage.py syncdb 5. Migrate changes. (archweb-env) $ ./manage.py migrate 6. Load the fixtures to prepopulate some data. If you don't want some of the provided data, adjust the file glob accordingly. (archweb-env) $ ./manage.py loaddata */fixtures/*.json 7. Use the following commands to start a service instance (archweb-env) $ ./manage.py runserver 8. To optionally populate the database with real data: (archweb-env) $ wget ftp://ftp.archlinux.org/core/os/i686/core.db.tar.gz (archweb-env) $ ./manage.py reporead i686 core.db.tar.gz (archweb-env) $ ./manage.py syncisos Alter architecture and repo to get x86\_64 and packages from other repos if needed. # Production Installation Ask someone who knows, or you are going to be in trouble. vim: set syntax=markdown et: