4.9 KiB
pict-rs 0.5.0
Overview
Headline Features
Changes
- Improved Animation Support
- Media Configuration
- Improved Collision Resistance
- Optional Video Transcoding
- Library API Changes
- Reject Malformed Deadliens
- Logging Verbosity
Other Features
- Quality Configuration
- Read-Only Mode
- Danger-Dummy Mode
- Media Variant Retention
- Configurable Temporary Directory
- Serve From Object Storage
- Prometheus Metrics
- Internal Hashes Endpoint
- Internal Delete Endpoint
- Error Codes
Fixes
Removals
Upgrade Notes
The upgrade from pict-rs 0.4 to 0.5 might take some time. Any uploads that have not had their
metadata extracted will be processed during this migration. In order to reduce the time required the
migration, pict-rs version 0.4.6 can be run first, and the /internal/prepare_upgrade endpoint can
be hit. This will tell pict-rs to extract the required metadata for the 0.5 upgrade in the
background while 0.4 is still running, enabling the upgrade to 0.5 to proceed much faster after it
completes. More information about this endpoint can be found in the
0.4.6 release document
If you're running the provided docker container with default configuration values, the 0.5 container can be pulled and launched with no changes. There is a migration from the 0.4 database format to the 0.5 database format that will occur automatically on first launch. This is also the process that will extract metadata for any uploads that have not had their metadata extracted yet.
If you have any custom configuration, note that some media-related configuration values have been moved. See Media Configuration below.
pict-rs 0.5 now supports postgres for metadata storage. It is possible to upgrade directly from 0.4 to 0.5 with postgres, rather than upgrading to 0.5 with sled and then making the migration later. This process is documented in the pict-rs readme.
More information can be found in the pict-rs 0.4 to 0.5 migration guide.
Descriptions
Postgres Repo
One of the most anticipated features of pict-rs 0.5 is the support for postgres for metadata storage. This makes pict-rs (mostly) stateless, enabling it to be scaled horizontally across multiple physical or virtual hosts. It also simplifies administration and backup processes for folks who are already running a postgres server for other reasons.
Configuring postgres is simple. The repo section of the pict-rs configuration now supports more
than just sled.
In the configuration file
[repo]
type = 'postgres'
url = 'postgres://user:password@host:5432/db'
With environment variables
PICTRS__REPO__TYPE=postgres
PICTRS__REPO__URL=postgres://user:password@host:5432/db
On the commandline
pict-rs run filesystem -p ./data postgres -u 'postgres://user:password@host:5432/db'
It is possible to update from 0.4 directly to 0.5 with postgres, this process is documented in the pict-rs readme.
It is possible to migrate to postgres after first upgrading to 0.5. This is also ducmented in the pict-rs readme.