Vue + Spring-Boot System handling plugin jams:
Following are the planned features:
- File uploading
- World upload
- Plugin upload (Superseded by 4.)
- Discord Bot Settings for TeamLeader
- Project Description
- Team name editing
- Link to Github
- Orga dashboard
- Team status
- active Deployments
- World downloads
- plugin jar downloads
- Server management
- Allow preinstalled framework selectionFrameworks
- Max Playercount
- Server restart
- Redeployment request
- Select which buildtool should be used (maven or gradle)
- Task selection
- Artifact path and file name declaration
- OAuth2
- Discord
We decided against a multistep docker image with a build step for the jar artifact. Observations have shown that the whole process took way longer than building the artifact local.
cd app
./gradlew clean build
cd ../docker/
docker-compose build
docker-compose up -d
nerdctl --namespace k8s.io compose build
kubectl apply -f kubernetes/database-persistence.yaml
to create persistence data claim separately. We don't want to lose the data when we redeploy.kubectl apply -k kubernetes
- Not adding the config file on image build instead
- Docker: Mount the config as volume
- Kubernetes: Create a configMap using the config file and mount it as well