#Is it possible to run immich_server and microservice on different hosts?

1 messages · Page 1 of 1 (latest)

nova coyote
#

My question arises from the fact that my NAS has a weak processor and cannot handle the image processing tasks of Immich. However, I also have another slightly more powerful All-in-One host. Considering the need for application integration, I would like to keep Immich deployed on the NAS, as most of my photos are stored on the NAS's Synology storage, but I would like to deploy the microservice on the more powerful host.

My current plan is to deploy the services normally on the NAS, but disable the microservice container. Meanwhile, I will deploy the same service on the All-in-One host, but modify the environment file to mount the upload and PostgreSQL addresses to the NAS's location, allowing both Compose setups to share the same database and external photo library. In this way, Immich1 would handle the server and web services, while Immich2 would handle the resource-intensive image processing. I'm wondering if this is the best practice for this kind of setup?

pulsar gustBOT
#

:wave: Hey @nova coyote,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: I have read applicable release notes.
  3. :blue_square: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
  7. :blue_square: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

red needle
#

You’ll want only one API worker, and then 1 or more microservices workers

#

The volume mounts need to be the same from within each container and they all need to have access to PG and Redis

nova coyote
acoustic sparrow