Skip to content

Commit fea8ef1

Browse files
committed
Updated and corrected the description in the README file of of how the contents of the bootstrap/dist/ directory end up in the right place for static serving.
- Legacy-Id: 10576
1 parent 8d56f46 commit fea8ef1

1 file changed

Lines changed: 9 additions & 3 deletions

File tree

bootstrap/README-DATATRACKER.rst

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,9 +61,15 @@ Available Grunt commands
6161
grunt dist # (Just compile CSS and JavaScript)
6262

6363
Regenerates the ``dist/`` directory with compiled and minified CSS and JavaScript
64-
files. As a Bootstrap user, this is normally the command you want. Changes to
65-
the ``dist/`` directory will be picked up by ``manage.py collectstatic`` as part
66-
of ``bin/mkrelease``.
64+
files. As a Bootstrap user, this is normally the command you want. Changes in the
65+
``dist/`` directory which are committed to the svn repository will be replicated in
66+
the ``ietf/static/ietf/bootstrap`` directory through and svn:externals declaration.
67+
68+
During development, you'll need to manually rsync newly generated files in place
69+
after doing ``grunt dist``: ``rsync -a dist/ ../ietf/static/ietf/bootstrap/``)
70+
71+
During deployment, they will be picked up by ``manage.py collectstatic`` and placed
72+
in the production environment's static directory.
6773

6874
::
6975

0 commit comments

Comments
 (0)