Some updates
Thoughts, Tips, and recent misadventures
Sep 14 2023
Some updates
Matrix migration
Switching from Synapse to Dendrite was always inevitable. I had dragged my feet on it largely due to an if it ain’t broke, don’t fix it mentality. The challenge was that eventually it did break. Somewhere between Synapse 1.8 and 1.9 I was unable to update without getting DB errors. I had tried a query based off someone having similar issues, but when the issue reappeared, it was for a different relation in the synapse db. This was when I decided to throw the towel and start fresh. Up until this time, my matrix instance has really only been for me and immediate family, and this was bound to happen because at the time of writing, you can’t migrate to dendrite and keep your messages.
Fixed! (Update)
I was wrong! if you migrate your videos with rclone
you can seamlessly update the video location on PeerTube by changing the base_url
parameter in your production.yaml file.
For misskey I’ve opened an issue for it
streaming_playlists:
bucket_name: 'streaming-playlists'
# Allows setting all buckets to the same value but with a different prefix
prefix: '' # Example: 'streaming-playlists:'
# Base url for object URL generation, scheme and host will be replaced by this URL
# Useful when you want to use a CDN/external proxy
base_url: '' # Example: 'https://mirror.example.com' # CHANGE THIS
# Same settings but for webtorrent videos
videos:
bucket_name: 'videos'
prefix: ''
base_url: '' #and this too!
Object storage Troubles
I’ve spent some time experimenting with S3 / Object Storage for public content.
I’ve found it useful for things like fediverse attachments & PeerTube videos.
Couple of updates
Contents
- PeerTube S3 Uploads
- Kuma
Troubleshooting PeerTube S3 uploads
In the interest of being cost-efficient I’ve setup my PeerTube to use object storage to store and serve the videos.
Steps
- Configure PeerTube
- Upload videos
- Configure CORS
Ensure you’ve got PeerTube setup.
From your peertube directory (or docker volume) you’ll want to update your config/local-production.json
/ config/localproduction.yaml
file.
NOTE:At the time of writing, Updating your server configuration from the management
console will ERASE your settings.
This means you’ll want to make sure to back up your settings so you can copy over your changes when needed.