Standalone Docker Compose file for local deployment

[iaktern]

• build docker image of Engine inside pipeline (if somethings changed in engine) and upload to Dockerhub
• build docker image of Standalone MS inside pipeline (with prisma applying schema to DB) and upload to Dockerhub
  • make the build of the MS inside the docker image and deleting the proceed code afterwards (no host architecture dependencies)
• the docker build file for creating the standalone system and the research system should nearly be the same, with the exception of the prisma migration part
• check/edit the docker-compose.yml (standalone file) and docker-compose.research.yml to:
  • 1. permissions to write into volume without having to do something at the host system
  • 2. which is the correct MS path for mapping to the volume (/home/nextjs/.config/proceed-management-system or /app/volume)
  • 3. maybe adapt (public) port mappings: MS needs port mapping, so it does not conflict with research MS; postgres and engine probably do not need port mapping because they should not be reachable from outside the server and just inside the docker network
  • 4. check if restart: always makes sense
• send both docker compose files via the Github pipeline to the research server (e.g. with scp). repull the newest images on the research server with docker compose pull. restart the research docker compose file.
• in another pipeline job: start the standalone compose file, run a short playwright test (admin login, passwort change, create new organization and a normal user inside, login with new user and change to organization, add the local Engine, create a process with one usertask and one script task, create version, deploy and instantiate the process, click the submit button inside the user task, check if the script task was run successfully), shutdown the standalone compose file, delete the db volume