mirror of
https://gitlab.com/signalytic/client-external/streamline/streamline-emr.git
synced 2026-09-11 18:51:31 +00:00
alec.turner
a424394109
The official image from streamline does not currently work for the arm64 platform. As a temporary measure, the source code and docker build scripts have been lifted from the official images and are used to build locally. Some additional modifications are made to reduce overall image size, these are documented in docker/README.md
Stre@mline
This is the official repository for Stre@mline.
How do I get set up?
-
Summary of set up
- This laravel application requires PHP 8+ and Composer for dependency management.
- Visit laravel documentation for updated laravel docs.
- Install Composer.
- Install the LAMP stack.
-
Configuration
- Run
git clone <this repository>andcdinto its root directory.
- Run
-
Dependencies
- Run
composer installto update the dependencies.
- Run
-
Database configuration
- Create the '.env' file (which is a copy of '.env.example') i.e.
cp .env.example .env - Set the database details (database, username, password)
- Run
php artisan key:generateto generate a unique key for the application. - Be sure to create the database; the tables and initial data will be auto-created by the next command.
- Run
php artisan migrate --seed - Run
php artisan serveto use the application on a local server. You will see a url in the command results.
- Run
- You can preferably run the application as you would a website on your operating system of choice.
- Create the '.env' file (which is a copy of '.env.example') i.e.
-
How to run tests
- Locally, you can set up a .env.testing for doing tests if you want.
- Run
phpunitto run all tests in the application. - Run
phpunit tests/feature/ExampleTest.phpTo test the file 'ExampleTest.php'.
- Run
- Remotely, visit pipelines to run all tests in the application.
- Locally, you can set up a .env.testing for doing tests if you want.
Managing Submodules
- After pulling:
- Run
git config user.nameandgit config user.passwordto set credentials and avoid being bothered with password requests - Then run
git submodule update --init --recursiveto initialize the modules - Then run
git submodule foreach --recursive git checkout mainto reset each submodule to main - And finally
git submodule foreach --recursive git pullto update the branch. You can use the two commands whenever you checkout to another branch
- Run
- If you make any changes within the Modules folder, commit to each repo affected and then commit to the container repo
- For more references, use the links below