Skip to Content
OpenBeacon
Use OpenBeaconSelf-hostContributePrivacy & security
Configuration

Picture storage

Profile and group pictures are stored in an S3-compatible bucket, such as Backblaze B2, MinIO or AWS S3.

The defaults for S3_ENDPOINT, S3_REGION and S3_CDN_URL point at OpenBeacon's own storage. Set all three to your own.

Set it up

  1. Create a bucket and set S3_BUCKET_NAME.
  2. Create an access key and set S3_ACCESS_KEY_ID and S3_ACCESS_KEY. The scheduled job runner's key also needs permission to delete objects, object versions and delete markers, so it can remove pictures when an account is deleted.
  3. Set S3_ENDPOINT and S3_REGION for your provider.
  4. Set S3_CDN_URL to the public address pictures are served from. Picture links are built from it.

Give the backend and the runner the same bucket and S3_CDN_URL.

At startup, both check they can list object versions in the bucket, and won't start if they can't.

Privacy

Pictures aren't end-to-end encrypted. Anyone who has a picture's address may be able to view it, depending on how your bucket and CDN are set up.

Google sign-in

Previous Page

Map tiles

The map needs a PMTiles file in a Cloudflare R2 bucket.

On this page

Set it upPrivacy