Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removes old Tilecloud chain documentation #5226

Merged
merged 1 commit into from
Aug 22, 2019
Merged

Removes old Tilecloud chain documentation #5226

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 3 additions & 26 deletions doc/integrator/tilegeneration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,9 +69,7 @@ See the `readme <https://pypi.python.org/pypi/tilecloud-chain>`_.
Configuration
~~~~~~~~~~~~~

The configuration is done in the file
``tilegeneration/config.yaml.tmpl``. The original file is available at:
https://github.com/camptocamp/c2cgeoportal/blob/2.4/geoportal/c2cgeoportal_geoportal/scaffolds/create/tilegeneration/config.yaml.tmpl_tmpl
The configuration is done in the file ``tilegeneration/config.yaml.tmpl``.

The main thing to do is to:

Expand All @@ -94,21 +92,9 @@ The main thing to do is to:
We consider that the first tile of the max zoom is empty.
Then copy-paste the result in the layer config.

* If you need it, you can generate the WMTS capabilities file:
If you generate the tiles locally, you do not need all the configuration variables, because many of them
in the ``generation`` part are for AWS generation.

.. prompt:: bash

docker-compose exec tilecloudchain generate_controller --generate-wmts-capabilities

* And an OpenLayers test page:

.. prompt:: bash

docker-compose exec tilecloudchain generate_controller --openlayers-test

If you generate the tiles locally, you do not need all the configuration
variables, because many of them in the ``generation`` part are for
AWS generation.

Tile Generation and management
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -136,12 +122,3 @@ If you setup all the default options, you can generate the tiles by using the co
.. prompt:: bash

docker-compose exec tilecloudchain generate_tiles

.. note:: Make sure you export AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY:

.. prompt:: bash

export AWS_ACCESS_KEY_ID=XXXXX
export AWS_SECRET_ACCESS_KEY=YYYY

If you forget it, you will get an error message.
2 changes: 2 additions & 0 deletions geoportal/c2cgeoportal_geoportal/scaffolds/update/CONST_CHANGELOG.txt_tmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@ Information
1. The SVG inclusion through Webpack has changed, See ngeo SVG example for more information:
https://camptocamp.github.io/ngeo/master/examples/svg.html

2. The WMTS capabilities is now generated on runtime.


Version 2.4.0
=============
Expand Down