env_example

## Make a copy of this file into .env and change the below fields
OBJECT_STORAGE_ENDPOINT="https://eu2.example.com"  # Object Storage
PICTRS_BUCKET="pictrs"  # Object Storage
AWS_ACCESS_KEY_ID=1234asdf5678zxxcvb890qwerty # Object Storage
AWS_SECRET_ACCESS_KEY=1234567890qwertyuiopasdfghjkl # Object Storage
AWS_DEFAULT_REGION=auto  # Remote Storage
SSH_HOSTNAME="127.0.0.1" # Remote Storage
SSH_PORT=22  # Remote Storage
SSH_USERNAME="root"  # Remote Storage: This user should have read/write access to your pict-rs files
SSH_PRIVKEY="/home/username/.ssh/id_rsa"  # Remote Storage: Path to your private key file. Windows systems path: Use c:\\path\\to\\saved\\private\\key
PICTRS_FILES_DIRECTORY="/lemmy/lemmy.example.com/volumes/pictrs/files"   # Remote/Local Storage: Path to your pictrs files directory. 
PICTRS_SAFETY_URL="http://lemmy.example.com:14051" # The URL where your pictrs-safety is reachable
PICTRS_SAFETY_APIKEY="abcdefg12345" # Should match FEDIVERSE_SAFETY_WORKER_AUTH you set in pirtrs-safety .env
# Set SQLITE_FILENAME here on in your local env before starting the fedi-safety so that you can change the sqlite filename
# This is useful if you scan multiple locations from the same installation
#SQLITE_FILENAME="lemmy_safety.db"