Go to file
str4d abb969b6cf Updated spectags
* ctags are case-sensitive, and the dataspecs use CamelCase.
* HTML anchor tags are case-sensitive. The old specs used CamelCase to match the
  ctags, and the existing documentation references them extensively.
* reStructuredText links are case-insensitive, and the HTML anchor tags that it
  generates are lower case.

Therefore, the links in the .rst files are given in CamelCase, and the dataspec
formatters convert this to lower case for links. In direct HTML references (in
specs or other areas of documentation), lower case must be used (to be fixed).

Command to generate the file:
cd i2p2www/spec && ctags -f spectags --langdef=rst --langmap=rst:.rst --regex-rst=/_type-\([a-zA-Z0-9]+\)/\\1/t,type/ --regex-rst=/_struct-\([a-zA-Z0-9]+\)/\\1/s,struct/ --regex-rst=/_msg-\([a-zA-Z]+\)/\\1/m,msg/ -R -n *.rst
2015-11-14 22:25:17 +00:00
2014-02-14 11:46:40 +00:00
2015-11-14 22:25:17 +00:00
2008-01-31 20:38:37 +00:00
2013-05-22 21:21:36 +00:00
2015-10-31 05:45:12 +00:00
2014-02-23 23:37:10 +00:00
2015-10-04 00:22:53 +00:00
2015-05-14 03:52:45 +00:00
2014-10-16 04:43:02 +00:00
2015-10-04 00:22:53 +00:00

I2P website

To run locally (for testing purposes):

  • Install proxychains, configure it for Tor

  • Pull in the dependencies:

    $ proxychains ./setup_venv.sh
    

    (you can also pull them non-anon by leaving out proxychains)

  • Compile translations (if you want to see them):

    $ ./compile-messages.sh
    
  • Start the webserver:

    $ ./runserver.py
    
  • Open the site at http://localhost:5000/

Running a mirror

If you want to mirror the I2P website, thanks! Here is a checklist:

  • Do not edit any of the files in i2p2www/
    • In particular, do not change the CANONICAL_DOMAIN variable in i2p2www/__init__.py, it needs to point to the official site for SEO.
  • If you need to edit variables in etc/update.vars, copy the file to etc/update.vars.custom and edit appropriately. The only variable you may need to edit is MTNURL in etc/update.vars (if your Monotone client tunnel is listening on a different port).
  • If you want to enable caching, copy i2p2www/settings.py.sample to i2p2www/settings.py and edit appropriately.
  • Add ./site-updater.sh to your crontab. This will keep the site updated, recompile the translations when necessary, and touch a file in /tmp/ (look in etc/update.vars for the filename, your webserver should restart WSGI when the timestamp of this file changes).

Updating translations

  1. Pull new and updated translations from Transifex:

    $ tx pull -a
    
  2. Correctly format the translations:

    $ ./update-existing-po.sh
    
  3. Check in the updated translations:

    $ mtn ci i2p2www/translations/ -m "Updated translations"
    
  4. Check in any new translations:

    $ mtn add -R i2p2www/translations/ && mtn ci i2p2www/translations/ -m "New translations"
    
  5. Update the POT files with any changes to the website text:

    $ ./extract-messages.sh
    
  6. Update the translations with any changes to the website text:

    $ ./update-existing-po.sh
    
  7. Check in any changes to the website text:

    $ mtn ci pots/ i2p2www/translations/ -m "Updated translation strings"
    
  8. Push website text changes to Transifex:

    $ tx push -s
    
Description
No description provided
Readme 270 MiB
Languages
HTML 80.9%
Python 8.3%
CSS 5.8%
TeX 4.1%
Shell 0.6%
Other 0.2%