Docker container

Open
#11 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker

Research direction

No files, tests, or entry points are named. Review the bot's current deployment and startup requirements, then define how the Docker container should be built and run. Done means the bot can be deployed successfully from the container with documented usage.

Written by the indexing model from the issue text.

Description

I am wondering if it would be worth getting the bot into a docker container to make it very easy to deploy

Dominant language
C#
Stars
3
Forks
2
Avg merge
15h 46m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GameServerManagers/LinuxGSM-Support-Bot

All issues in GameServerManagers/LinuxGSM-Support-Bot

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.