AToMPM / AToMPM/atompm

Deploy Docker image to a server

Open
#149 0 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue help wanted Test/CI/CD
Dominant language
JavaScript
Stars
25
Forks
15
PR merge metrics
No merged PRs in 30d

Description

It was always intended that there be an AToMPM instance running on a public-facing server. With the creation of the Docker image, this is now possible.

Concrete tasks include:
* Ensuring the [Docker file](https://github.com/AToMPM/atompm/blob/master/packaging/docker/Dockerfile), [Docker instructions](https://github.com/AToMPM/atompm/blob/master/packaging/docker/README.md), and [GitHub workflow](https://github.com/AToMPM/atompm/blob/master/.github/workflows/make_docker.yml) are up-to-date
* Coordinating with Eugene and IT at UdeM for server access
* Coming up with a policy for rebooting the image when it crashes
* Should the image be periodically restarted, and possibly wiped? How can users be informed that this image is temporary?
* Creating a workflow for Docker container deployment on new tags/releases in the repo

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with packaging/docker/Dockerfile, packaging/docker/README.md, and .github/workflows/make_docker.yml to understand the existing image and workflow. Then review the server-access coordination, crash-restart and temporary-instance policy, and deployment on new tags or releases. Done means a documented, maintainable deployment process is agreed and operational.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, github-actions
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.