Gaming/ansible-role-vintage-story
1
0
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Inititial setup #2

Merged
eric merged 3 commits from init into main 2025-09-12 17:38:20 +00:00
Conversation 1 Commits 3 Files Changed 8 +876
eric commented 2025-09-12 02:52:43 +00:00
Owner
Copy Link

Deploying Vintage Story to Kubernetes


In this live stream I am initializing an Ansible role for deploying Vintage Story to a Kubernetes cluster as part of my software-infrastructure. While I typically prefer to use Helm charts for my deployments, I have not found one suitable for Vintage Story, so the initial version of this repository will simply define the necessary resources to deploy the devidian/vintagestory Docker container and supporting resources. This PR also contains a copy of the default serverconfig.json, which, at present, needs to be edited and copied to the underlying PVC manually. While a functional server was achieved by the end of this live stream, this PR will remain a WIP to address Gaming/ansible-role-vintage-story#1, which seeks to improve on this deployment process. Additional issues may be added to support the start of Season I of Vintage Story on eom.dev.

# Deploying Vintage Story to Kubernetes <video controls type="video/mp4" src="https://minio.eom.dev/public/Videos/2025-09-11_20-09-58.mp4"></video> In this live stream I am initializing an Ansible role for deploying Vintage Story to a Kubernetes cluster as part of my [software-infrastructure](https://gitea.eom.dev/DevOps/software-infrastructure). While I typically prefer to use Helm charts for my deployments, I have not found one suitable for Vintage Story, so the initial version of this repository will simply define the necessary resources to deploy the [devidian/vintagestory](https://hub.docker.com/r/devidian/vintagestory) Docker container and supporting resources. This PR also contains a copy of the default `serverconfig.json`, which, at present, needs to be edited and copied to the underlying PVC manually. While a functional server was achieved by the end of this live stream, this PR will remain a WIP to address Gaming/ansible-role-vintage-story#1, which seeks to improve on this deployment process. Additional issues may be added to support the start of [Season I of Vintage Story on eom.dev](https://discourse.eom.dev/t/season-i-megathread/341?u=eric).
eric added 2 commits 2025-09-12 02:52:44 +00:00
eric added spent time 2025-09-12 03:08:21 +00:00
1 hour 42 minutes
eric added 1 commit 2025-09-12 17:32:09 +00:00
eric changed title from WIP: Inititial setup to Inititial setup 2025-09-12 17:35:43 +00:00
eric merged commit 137e8279db into main 2025-09-12 17:38:20 +00:00
eric deleted branch init 2025-09-12 17:38:24 +00:00
eric referenced this issue from a commit 2025-09-12 17:38:25 +00:00
Inititial setup (#2)
eric commented 2025-09-12 18:02:10 +00:00
Author
Owner
Copy Link

Kubernetes ConfigMap within a PVC for Vintage Story Server


Continuing with the Vintage Story server deployment, this stream documents an experiment in deploying a Kubernetes ConfigMap within a PersistentVolume. This can be useful when a pod stores application data alongside configuration files, as it allows for mounting a templated file within a persistent filesystem. More work is needed to fully utilize this interface, as is described in Gaming/ansible-role-vintage-story#3, but for now this PR will be closed as it establishes the basic method for deploying and configuring Vintage Story on Kubernetes.

# Kubernetes ConfigMap within a PVC for Vintage Story Server <video controls type="video/mp4" src="https://minio.eom.dev/public/Videos/2025-09-12_12-44-39.mp4"></video> Continuing with the Vintage Story server deployment, this stream documents an experiment in deploying a Kubernetes [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) within a [PersistentVolume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/). This can be useful when a pod stores application data alongside configuration files, as it allows for mounting a templated file within a persistent filesystem. More work is needed to fully utilize this interface, as is described in Gaming/ansible-role-vintage-story#3, but for now this PR will be closed as it establishes the basic method for deploying and configuring Vintage Story on Kubernetes.
eric added spent time 2025-09-12 18:02:24 +00:00
56 minutes
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Total Time Spent: 2 hours 38 minutes
eric
2 hours 38 minutes
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Gaming/ansible-role-vintage-story#2
No description provided.
Delete Branch "init"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?