Skip to content

Release 1.1.0

Latest
Latest
Compare
Choose a tag to compare
@jdtriska jdtriska released this 27 Mar 00:53
1.1.0
cd73d37

Some great changes in this release!

Bugfixes

  • Fixed nginx conf via startup script to support full load balancer domain as server name.
  • Added flock to sync script to ensure long-running syncs do not overlap.

Breaking Changes

  • EBS_VOLUME_SIZE has been renamed to EBS_ROOT_VOLUME_SIZE
  • EBS_MEDIA_VOLUME_SIZE and EBS_MEDIA_VOLUME_TYPE have been added as required .env variables
  • A lot of networking has changed, as well as the EC2 instance configuration, which will force you to re-create your instance since it will be deployed in an entirely new VPC. Please back up your ~/jellyfin/config folder manually to your local machine before running the terraform apply command. You can then restore that folder to the newly created Jellyfin server to start from where you left off. The new configuration will also come with basic backup and restore scripts to automatically backup your Jellyfin configuration to S3, and restore at will.

New features

  • Jellyfin instance is now deployed in separate VPC.
  • Backup and restore scripts (~/jellyfin/scripts/backup.sh and ~/jellyfin/scripts/restore.sh) for your Jellyfin config are now created with your instance which allow you to backup and restore from S3.
  • Automatic backups (~/jellyfin/scripts/start-backup.sh) of your Jellyfin config are made every hour, and retained for 30 days by default.
  • A separate EBS volume is now created and mounted to the ~/jellyfin/media folder. This allows you to store your media on a separate EBS volume with a custom volume type. I would suggest scaling down your root volume size and running a larger, magnetic media volume.

Special thanks to @dougkirkley for lots of great refactoring and EBS+VPC terraform.

Assets 2
Loading