🏗️ New Service: mail archiver
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, docker-compose, postgresql
- Domain
- devops, infrastructure
Research direction
Use the linked mail-archiver docker-compose.yml as the deployment reference, then inspect ScaleTail's existing service entries and contribution conventions to find where this service belongs. Add the mail-archiver entry using the provided configuration and verify that it matches the repository's expected Docker sidecar setup.
Written by the indexing model from the issue text.
Description
Service Description
Hi team
Would you consider creating an entry for mail archiver? Currently looking to add this to my tailnet!
Thanks a million
Docker Compose File Link
https://github.com/s1t5/mail-archiver/blob/main/docker-compose.yml
Docker Compose Configuration
version: '3.8'
networks:
postgres:
services:
mailarchive-app:
build: .
restart: always
ports:
- "5000:5000"
networks:
- postgres
# Uncomment the following line to mount a directory for local file imports
# (also add the path to appsettings.json: LocalImport.AllowedPaths)
# - /path/to/your/mbox/files:/data/import
- ./appsettings.json:/app/appsettings.json
- ./logs:/app/logs
- ./data-protection-keys:/app/DataProtection-Keys
depends_on:
- postgres
postgres:
image: postgres:14-alpine
restart: always
environment:
POSTGRES_DB: MailArchiver
POSTGRES_USER: mailuser
POSTGRES_PASSWORD: masterkey
volumes:
- ./postgres-data:/var/lib/postgresql/data
networks:
- postgres
healthcheck:
test: ["CMD-SHELL", "pg_isready -U mailuser -d MailArchiver"]
interval: 10s
timeout: 5s
retries: 5
start_period: 10s
Website of Service
Would you be willing to work on this service?
- Yes, I'd like to implement this feature
- I could help with parts of this feature
- No, I'm just suggesting the feature
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 127
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from tailscale-dev/ScaleTail
-
new service
Difficulty 3/5 1-2 days Newbie friendliness 45/100
tailscale-dev/ScaleTail#341 ·
Maintainers usually reply within 1 day
-
new service
Difficulty 4/5 3-5 days Newbie friendliness 48/100
tailscale-dev/ScaleTail#335 ·
Maintainers usually reply within 1 day
-
new service
Difficulty 4/5 3-5 days Newbie friendliness 30/100
tailscale-dev/ScaleTail#325 ·
Maintainers usually reply within 1 day
-
new service
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
tailscale-dev/ScaleTail#322 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
tailscale-dev/ScaleTail#317 ·
Maintainers usually reply within 1 day
All issues in tailscale-dev/ScaleTail
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
war-and-code/dircue#200 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day