Testing
Go to file
Dan McGee 7c70083ed5 Cleanups and enhancments to JS package search typeahead
Remove the need to press enter twice when using this typeahead box.
Submit the form on enter, regardless of whether an item is selected or
not.

Signed-off-by: Dan McGee <dan@archlinux.org>
2014-01-27 17:27:54 -06:00
devel Revert "Change old packages report from two years to one year" 2014-01-26 12:55:33 -06:00
main
mirrors Add a 'last_modified' function for mirror status pages 2014-01-11 13:37:12 -06:00
news
packages Add 'Latest Update' column to stale package relations 2014-01-25 09:16:48 -06:00
public
releng
retro
sitestatic Fix linebreak issues in preformatted code blocks 2014-01-27 13:17:49 -06:00
templates Cleanups and enhancments to JS package search typeahead 2014-01-27 17:27:54 -06:00
todolists
visualize
__init__.py
.gitattributes
.gitignore
archweb.wsgi
AUTHORS
feeds.py Speed up feeds generation by batching writes 2014-01-11 13:07:40 -06:00
HACKING
LICENSE
local_settings.py.example
manage.py
newrelic.ini
README
README.md
requirements_prod.txt Bump pgpdump required version 2014-01-27 10:17:56 -06:00
requirements.txt Bump pgpdump required version 2014-01-27 10:17:56 -06:00
settings.py
sitemaps.py
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
    
  3. Install dependencies through pip.

     (archweb-env) $ pip install -r requirements.txt
    
  4. Copy local_settings.py.example to local_settings.py and modify. Make sure to uncomment the appropriate database section (either sqlite or PostgreSQL).

  5. Sync the database to create it.

     (archweb-env) $ ./manage.py syncdb
    
  6. Migrate changes.

     (archweb-env) $ ./manage.py migrate
    
  7. 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
    
  8. Use the following commands to start a service instance

     (archweb-env) $ ./manage.py runserver
    
  9. 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: