refactor: move backend to monorepo

backend/.gitlab/ci/getRegistryBranch.sh

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+
+# script returns string with everything after the last colon of $1 input
+echo -n $1 | grep -oE '[^:]+$'

backend/.gitlab/ci/getRegistryTag.sh

@@ -0,0 +1,8 @@
+#!/usr/bin/env sh
+
+# script returns semantical versioning string linke 2.0.0 (if $1 is v2.0.0) or $1
+if echo -n $1 | grep -Eq 'v[0-9]+\.[0-9]+\.[0-9]+'; then 
+  echo $(echo -n "$1" | cut -c 2-);
+else 
+  echo $1;
+fi

backend/.gitlab/ci/pushAsLatestVersion.sh

@@ -0,0 +1,7 @@
+#!/usr/bin/env sh
+
+# If this is a pipeline of a version tag, also push this version 
+# as latest to the registry alias $2:latest
+if echo -n $1 | grep -Eq 'v[0-9]+\.[0-9]+\.[0-9]+'; then
+  docker push $2:latest;
+fi

backend/.gitlab/ci/testCIScripts.sh

@@ -0,0 +1,29 @@
+#!/usr/bin/env sh
+
+# test all CI scripts
+
+SCRIPT_DIR=$(dirname "$0")
+
+TAG_VERSION=$(sh $SCRIPT_DIR/getRegistryTag.sh "v1.0.0")
+TAG_TEST=$(sh $SCRIPT_DIR/getRegistryTag.sh "TEST")
+BRANCH_NAME=$(sh $SCRIPT_DIR/getRegistryBranch.sh "very:first:test")
+
+# Leaving out pushAsLatestVersion.sh as its controll flow
+# is based on the same condition as getRegistryTag.sh
+
+if [ $TAG_VERSION != "1.0.0" ]; then
+	echo "ERROR in CI SCRIPT: $SCRIPT_DIR/getRegistryTag.sh"
+	return 1
+fi
+
+if [ $TAG_TEST != "TEST" ]; then
+	echo "ERROR in CI SCRIPT: $SCRIPT_DIR/getRegistryTag.sh"
+	return 2
+fi
+
+if [ $BRANCH_NAME != "test" ]; then
+	echo "ERROR in CI SCRIPT: $SCRIPT_DIR/getRegistryBranch.sh"
+	return 3
+fi
+
+return 0

backend/.gitlab/issue_templates/bug.md

@@ -0,0 +1,41 @@
+## Summary
+
+(Summarize the bug encountered concisely)
+
+
+## Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+
+## Example Project
+
+(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
+
+(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)
+
+## Which version of the software did you use ?
+
+(Version numbers of used software or commit references)
+
+## What is the current bug behavior?
+
+(What actually happens)
+
+
+## What is the expected correct behavior?
+
+(What you should see instead)
+
+
+## Relevant logs and/or screenshots
+
+(Paste any relevant logs - please use code blocks (```) to format console output,
+logs, and code as it's very hard to read otherwise.)
+
+
+## Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/label ~bug ~meeting

backend/.gitlab/issue_templates/feature.md

@@ -0,0 +1,20 @@
+## Description
+
+(Describe the feature that you're requesting concisely)
+
+
+## Explanation
+
+(Explain why the feature is necessary)
+
+
+## Mockups/Data
+
+(If possible, provide mockups or examples of communication, which demonstrate the feature)
+
+
+## Dependencies, issues to be resolved beforehand
+
+(List issues or dependencies that need to be resolved before this feature can be implemented)
+
+/label ~feature ~meeting