lemmy/docker
Dessalines ee7df0dc35 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
2024-05-05 21:47:02 -04:00
..
federation Upgrading from postgres 15 -> 16-alpine. (#4426) 2024-02-07 11:21:02 +01:00
docker-compose.yml Adding an image_details table to store image dimensions. 2024-05-05 21:47:02 -04: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 chore(deps): update docker/dockerfile docker tag to v1.7 (#4650) 2024-04-19 18:12:26 -04:00
lemmy.hjson Fix image_mode for docker lemmy.hjson (#4403) 2024-01-26 10:51:59 +01: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