From fea8ef1d34fd0e8ef4fcc3ccf5c119e4ed5b63ab Mon Sep 17 00:00:00 2001 From: Henrik Levkowetz Date: Fri, 11 Dec 2015 11:25:15 +0000 Subject: [PATCH] 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 --- bootstrap/README-DATATRACKER.rst | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/bootstrap/README-DATATRACKER.rst b/bootstrap/README-DATATRACKER.rst index 2b682998d..f088cc2cc 100644 --- a/bootstrap/README-DATATRACKER.rst +++ b/bootstrap/README-DATATRACKER.rst @@ -61,9 +61,15 @@ Available Grunt commands grunt dist # (Just compile CSS and JavaScript) Regenerates the ``dist/`` directory with compiled and minified CSS and JavaScript -files. As a Bootstrap user, this is normally the command you want. Changes to -the ``dist/`` directory will be picked up by ``manage.py collectstatic`` as part -of ``bin/mkrelease``. +files. As a Bootstrap user, this is normally the command you want. Changes in the +``dist/`` directory which are committed to the svn repository will be replicated in +the ``ietf/static/ietf/bootstrap`` directory through and svn:externals declaration. + +During development, you'll need to manually rsync newly generated files in place +after doing ``grunt dist``: ``rsync -a dist/ ../ietf/static/ietf/bootstrap/``) + +During deployment, they will be picked up by ``manage.py collectstatic`` and placed +in the production environment's static directory. ::