Move lists server into the infrastructure project
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
The lists server already runs on Digital Ocean, but not yet in the infrastructure managed through Ansible.
As the server does not do any delivery or receiving of email directly, DO is fine for it.
It is a little uncertain how everything is set up on the machine, but there is the possibility that I have notes on this from when I set it up in early 2025.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the lists server currently runs on Digital Ocean and searching for any setup notes from early 2025. Then inspect the repository's Ansible playbooks to determine where the server belongs. Done means the lists server is represented and managed through this infrastructure project without disrupting its existing operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100