Testing
Go to file
Dan McGee e969da2d40 Run pngcrush and optipng over most static content
The programs have improved a bit and found some room for optimization,
especially in the static logo content. Some files were reduced in size
by 50% or more.

Signed-off-by: Dan McGee <dan@archlinux.org>
2013-02-03 13:38:39 -06:00
devel Handle connection and transaction more properly in reporead 2013-01-15 20:49:56 -06:00
main Fix error in get_requiredby() when checking provides 2013-01-20 15:28:17 -06:00
mirrors Lengthen the mirror rsync IP address field 2013-01-20 15:01:13 -06:00
news
packages Use more modern verison of string template formatting 2013-01-23 09:20:19 -07:00
public Run pngcrush and optipng over most static content 2013-02-03 13:38:39 -06:00
releng Extract torrent trackers into a settings variable 2013-01-28 14:13:53 -07:00
retro Run pngcrush and optipng over most static content 2013-02-03 13:38:39 -06:00
sitestatic Spice up the release listing page a bit 2013-01-22 20:21:40 -07:00
templates Merge branch 'release' 2013-01-28 23:56:30 -06:00
todolists Show staging version on todolist view page 2013-01-22 16:47:43 -06:00
visualize
__init__.py
.gitattributes
.gitignore
archweb.wsgi
AUTHORS
feeds.py Add basic release list and details views 2013-01-19 12:08:31 -06:00
HACKING
LICENSE
local_settings.py.example
manage.py
newrelic.ini
README
requirements_prod.txt Implement torrent data parsing and extraction via bencode 2013-01-19 13:08:06 -06:00
requirements.txt Implement torrent data parsing and extraction via bencode 2013-01-19 13:08:06 -06:00
settings.py Extract torrent trackers into a settings variable 2013-01-28 14:13:53 -07:00
sitemaps.py Include 'files_last_update' in package sitemap query 2013-01-18 20:15:40 -06:00
TODO
urls.py Slight reorganization of urls.py 2013-01-21 11:08:35 -06:00

# 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: