Repository navigation
Expand file tree
/
Copy path.env.example
More file actions
73 lines (70 loc) · 2.8 KB
/
Copy path.env.example
File metadata and controls
73 lines (70 loc) · 2.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
# POSSE Configuration Example
# NOTE: This project uses config.yml for configuration and Docker secrets
# for sensitive credentials stored in the secrets/ directory.
#
# For production and local development:
# 1. Create secrets directory: mkdir -p secrets
# 2. Add your secrets (use a text editor or printf to avoid shell history):
# printf '%s' 'your_token' > secrets/pushover_app_token.txt
# printf '%s' 'your_key' > secrets/pushover_user_key.txt
# 3. Enable in config.yml: pushover.enabled: true
#
# For CI/CD (GitHub Actions):
# - Configure secrets in repository settings (PUSHOVER_APP_TOKEN, PUSHOVER_USER_KEY)
# - Secrets are automatically written to files during workflow execution
#
# Legacy environment variable support (not recommended):
# PUSHOVER_APP_TOKEN=your_pushover_app_token_here
# PUSHOVER_USER_KEY=your_pushover_user_key_here
# Mastodon Configuration
# POSSE now supports multiple Mastodon accounts!
#
# Multi-account setup:
# 1. Create secret files for each account using naming convention:
# {platform}_{account_name}_{credential_type}
#
# mkdir -p secrets
# printf '%s' 'your_personal_token' > secrets/mastodon_personal_access_token.txt
# printf '%s' 'your_work_token' > secrets/mastodon_work_access_token.txt
#
# 2. Configure accounts in config.yml:
# mastodon:
# accounts:
# - name: "personal"
# instance_url: "https://mastodon.social"
# access_token_file: "/run/secrets/mastodon_personal_access_token"
# - name: "work"
# instance_url: "https://fosstodon.org"
# access_token_file: "/run/secrets/mastodon_work_access_token"
#
# 3. Add secrets to docker-compose.yml:
# secrets:
# mastodon_personal_access_token:
# file: ./secrets/mastodon_personal_access_token.txt
# mastodon_work_access_token:
# file: ./secrets/mastodon_work_access_token.txt
#
# To get an access token for each account:
# 1. Go to your Mastodon instance settings
# 2. Navigate to Development -> New Application
# 3. Create a new application with 'write:statuses' scope
# 4. Copy the access token and save to appropriate secret file
# Bluesky Configuration
# POSSE supports multiple Bluesky accounts with the same structure as Mastodon!
#
# Multi-account setup example:
# mkdir -p secrets
# printf '%s' 'your_main_token' > secrets/bluesky_main_access_token.txt
# printf '%s' 'your_professional_token' > secrets/bluesky_professional_access_token.txt
#
# Configure in config.yml:
# bluesky:
# accounts:
# - name: "main"
# instance_url: "https://bsky.social"
# access_token_file: "/run/secrets/bluesky_main_access_token"
# - name: "professional"
# instance_url: "https://bsky.social"
# access_token_file: "/run/secrets/bluesky_professional_access_token"
#
# For a single account, simply configure one account in the accounts array.