lemmy/docker
Dessalines 426684d90f
Adding blurhash to image_details. (#5227)
* Adding blurhash to image_details.

- Fixes #5142

* Using new pictrs to get blurhash.

* Fixing ts-binding.

* Addressing PR comments.

* Commenting checks.

* Switching back to rust 1.81.

* Adding diesel schema

* Adding database user creation.

* Specific tests.

* Upping pictrs to 0.5.17-pre.9

* Fixing

* Using full tests.

* Fixing pictrs hash.

* Upgrading pnpm deps.
2025-02-10 17:27:22 -05:00
..
federation Adding blurhash to image_details. (#5227) 2025-02-10 17:27:22 -05:00
docker-compose.yml Adding blurhash to image_details. (#5227) 2025-02-10 17:27:22 -05:00
docker_db_backup.sh make shebangs posix compliant (#2974) 2023-06-08 15:38:26 -04:00
docker_update.sh Avoid using proxy for pictrs requests (fixes #3489) (#4072) 2023-10-20 11:09:34 -04:00
Dockerfile Removing upx. (#5388) 2025-02-04 11:15:27 -05:00
lemmy.hjson Only accept database connection by uri (#5254) 2024-12-10 10:15:54 -05:00
nginx.conf Adding /version route. Fixes #2914 (#4059) 2023-10-24 10:49:52 +02:00
README.md fix: Cross-compilation to ARM64 (#4142) 2023-11-24 12:52:19 -05:00
test_deploy.sh Adding current domain from settings to CORs. (#3231) 2023-06-20 20:29:48 -04:00

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.

References