You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 4, using s/docker-init, doesn’t work. Need to specify the local-dev.yml file with sudo docker compose -f docker-compose.local-dev.yml exec web coverage run manage.py test
Note - this and other local-dev.yml problems I found can all be fixed by changing the command in the respective s/scripts
change all instances of a docker compose command over to use the relevant s/docker-* script
When executing commands in the context of the web container, you need to have an active shell prompt, but the terminal is non-functional while the rcpch-audit-engine is being used in the same terminal.
Add instruction to open another terminal window
Running docker compose down:
Need to use the -f flag and specify which docker configuration file to use (fixable using s/scripts)
Running tests
Most recent instruction in Docs before this page is to close and destroy the Docker container. Should specify that before you run pytest, you need to have the Docker container built.
Docker file specified is docker-compose.dev-init.yml. Should it not be .local-dev.yml if in the development branch (fixable with s/script changes)
Change this in the s/docker-compose.local-dev.yml file
Customisation and Useful Flags
In the various code blocks throughout the page, there is the term ‘console’ from the .md file leaking into the webpage. This also removes the functionality of copying the command directly from the ‘copy’ button that mkdocs gives to the console boxes
fix any malformed code blocks
Running the specific test_length_of_treatment Pytest doesn’t work, can’t locate the test
Docker setup
Step 4, using s/docker-init, doesn’t work. Need to specify the local-dev.yml file with sudo docker compose -f docker-compose.local-dev.yml exec web coverage run manage.py test
docker compose
command over to use the relevants/docker-*
scriptWhen executing commands in the context of the web container, you need to have an active shell prompt, but the terminal is non-functional while the rcpch-audit-engine is being used in the same terminal.
Running docker compose down:
Running tests
Customisation and Useful Flags
In the various code blocks throughout the page, there is the term ‘console’ from the .md file leaking into the webpage. This also removes the functionality of copying the command directly from the ‘copy’ button that mkdocs gives to the console boxes
Running the specific test_length_of_treatment Pytest doesn’t work, can’t locate the test
Test structure
_meta_tests
Factories and Fixtures
Code Style
Logos and Branding
Project Structure
Design decisions and rationale
Organisations, Trusts and Levels of Abstraction
Scoring the audit forms
The text was updated successfully, but these errors were encountered: