Review file organisation

[milanmlft]

Definition of Done / Acceptance Criteria

We have reviewed the current organisation of configuration and source files and determined whether it's the most optimal setup.

Testing

• All tests should still pass
• Pre-processing scripts should still run successfully

Documentation

No response

Dependencies

No response

Details and Comments

It might make sense to move the shiny app to a subdirectory of this repo and have the configuration and deployment files (.env, docker-compose.yml, ...) and the pre-processing scripts (currently in dev/ subfolders) live in the root of the repo.

Work out whether we think changing the structure is worthwhile.

[linear]

SAF-645 Review file organisation

Definition of Done / Acceptance Criteria

We have reviewed the current organisation of configuration and source files and determined whether it's the most optimal setup.

Testing

No response

Documentation

No response

Dependencies

No response

Details and Comments

It might make sense to move the shiny app to a subdirectory of this repo and have the configuration and deployment files (.env, docker-compose.yml, ...) and the pre-processing scripts (currently in dev/ subfolders) live in the root of the repo.

[milanmlft]

Suggestions:

• Move dev/test_db to data/test_db
• Move dev/omop_analyses/ and dev/test_db/*.R to scripts/
• Add data and scripts to .Rbuildignore
• Keep current package structure (i.e. don't move it to a subdir of the repo)