55f84dd38a
* Adding an image_details table to store image dimensions. - Adds an image_details table, which stores the height, width, and content_type for local and remote images. - For LocalImages, this information already comes back with the upload. - For RemoteImages, it calls the pictrs details endpoint. - Fixed some issues with proxying non-image urls. - Fixes #3328 - Also fixes #4703 * Running sql format. * Running fmt. * Don't fetch metadata in background for local API requests. * Dont export remote_image table to typescript. * Cleaning up validate. * Dont proxy url. * Fixing tests, fixing issue with federated thumbnails. * Fix tests. * Updating corepack, fixing issue. * Refactoring image inserts to use transactions. * Use select exists again. * Fixing imports. * Fix test. * Removing pointless backgrounded metadata generation version. * Removing public pictrs details route. * Fixing clippy. * Fixing proxy image fetching. Fixes #4703 - This extracts only the proxy image fixes from #4704, leaving off thumbnails. * Fix test. * Addressing PR comments. * Address PR comments 2. --------- Co-authored-by: SleeplessOne1917 <28871516+SleeplessOne1917@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| federation | ||
| docker-compose.yml | ||
| docker_db_backup.sh | ||
| docker_update.sh | ||
| Dockerfile | ||
| lemmy.hjson | ||
| nginx.conf | ||
| README.md | ||
| test_deploy.sh | ||
Building Lemmy Images
Lemmy's images are meant to be built on linux/amd64,
but they can be executed on both linux/amd64 and linux/arm64.
To do so we need to use a cross toolchain whose goal is to build from amd64 to arm64.
Namely, we need to link the lemmy_server with pq and openssl
shared libraries and a few others, and they need to be in arm64,
indeed.
The toolchain we use to cross-compile is specifically tailored for Lemmy's needs, see the image repository.