Mercurial > p > roundup > code
view website/www/code.txt @ 6994:4336e655b2be
Update packages in docker image; supress pip warning; improve cache
use apk to update packages in image to get security fixes
pip warns when run as root. In a dcker environment this can be ignored
as the entire image is effectively a venv.
Move inclusion of specific pip packages lower in the build procedure
so we can cache all prior layers. Including it earlier resulted in
layers that could be cached being invalidated.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 01 Oct 2022 23:40:48 -0400 |
| parents | 45e8d10a9609 |
| children | 6f5054751fb6 |
line wrap: on
line source
Code ==== Project history is maintained in `CHANGES.txt <https://sourceforge.net/p/roundup/code/ci/tip/tree/CHANGES.txt>`_ file in code repository of Roundup, which can also be viewed online through SourceForge `web interface <https://sourceforge.net/p/roundup/code/ci/default/tree/>`_. Get sources ----------- Official **read-only access** to Mercurial repository is provided through :: hg clone http://hg.code.sf.net/p/roundup/code roundup **Read/write access** requires SSH password or SSH key authorization (see `SourceForge.net docs for details <https://sourceforge.net/p/forge/documentation/Mercurial/>`_) :: hg clone ssh://USERNAME@hg.code.sf.net/p/roundup/code roundup You also need to be added as a Roundup developer for write access - ask for it on the :doc:`roundup-devel list <contact>`. Run demo -------- Roundup doesn't need any dependencies and works out of the box. Demo is accessible at http://localhost:8917/demo/ by default :: cd roundup python demo.py Execute tests ------------- :: python run_tests.py See repository `README.txt <https://sourceforge.net/p/roundup/code/ci/tip/tree/README.txt>`_ for more info.