| Age | Commit message (Collapse) | Author |
|---|
|
xargs sed -ri \
-e 's|Arch Linux|{{ BRANDING_DISTRONAME }}|g' \
-e 's|https://wiki.archlinux.org/index.php/([^ "]*)|{% wiki_url '\''\1'\'' %}|g' \
-e 's|https://mailman.archlinux.org|{{ MAILMAN_BASE_URL }}|g' \
-e 's|<a href="https://bugs.archlinux.org/task/\{\{\s*([^ }])\s*}}>FS#\{\{\s*([^ }])\s*}}</a>|{% bug_link \1 %}|g' \
--
|
|
I added this a while back, but didn't roll it out to all templates.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This is now the default in Django 1.5.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This is a lot more flexible and will allow more than just simple
prefixing of the static file resources.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
The old-style url template tag disappears in Django 1.5, so we can and
should convert to the new-style tag now.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This moves our site static files into the sitestatic directory if they
are shared resources, and also moves a handful of things (such as the
artwork logos) into application-specific static/ directories. This
allows the staticfiles contrib app to work after a few settings tweaks,
a run of collectstatic, and massaging the hardcoded '/media/' prefix out
of our templates.
Django 1.4 is going to make this a lot easier to move things to a CDN
and provides better template tags; for now this is setting the stage
before we can move to that.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Well, almost add it- it is currently commented out as I have a few more
things I'd like to take care of, namely correcting static files
versioning and caching, to ensure this doesn't break things.
This is a force-directed graph drawn using D3 as the package treemap
already does. We color the dots by "group", e.g. "dev", "tu", or
"master", and then outline developer keys in green if they have at least
3 master key signatures, red if they have fewer. Hovering over a circle
will show you who's key you are seeing in the visualization.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Why the hell not? Have fun clicking all the pretty buttons.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
