self-hosted/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-12-12 08:43:55 +02:00
Code Issues Releases Activity
5733f4d157
matrix-docker-ansible-deploy/docs/alternative-architectures.md
Slavi Pantaleev de545f9c5f Update docs on self-building and remove useless variable 
`matrix_container_images_self_build` was not really doing anything
anymore. It previously was influencing `matrix_*_self_build` variables,
but it's no longer the case since some time ago.

Individual `matrix_*_self_build` variables are still available.
People that would like to toggle self-building for a specific component
ought to use those.

These variables are also controlled automatically (via
`group_vars/matrix_servers`) depending on `matrix_architecture`.

In other words, self-building is being done automatically for
all components when they don't have a prebuilt image for the specified
architecture. Some components only support `amd64`, while others also
have images for other architectures.
2020-06-29 14:58:03 +03:00

1006 B
Raw Blame History

Alternative architectures

As stated in the Prerequisites, currently only x86_64 is fully supported. However, it is possible to set the target architecture, and some tools can be built on the host or other measures can be used.

To that end add the following variable to your vars.yaml file:

matrix_architecture: <your-matrix-server-architecture>

Currently supported architectures are the following:

  • amd64 (the default)
  • arm64
  • arm32

so for the Raspberry Pi, the following should be in your vars.yaml file:

matrix_architecture: "arm32"

Implementation details

For amd64, prebuilt images are used everywhere (because all images are available for this architecture).

For other architectures, components which have a prebuilt image make use of it. If the component is not available for the specific architecture, self-building will be used. Not all components support self-building though, so your mileage may vary.