tailscale-dev / tailscale-dev/ScaleTail
🏗️ New Service: mail archiver
Open
Nobody has claimed this yet.
new service
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 124
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 4
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
Contributor 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.
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.
Assessment
- Tech stack
- docker, docker-compose, postgresql
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100