Create a new immich-server config sample. #721
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Immich's official docker-compose.yml uses the main immich service as
immich_server
, as per discussion in #713 the feedback was to create a new config instead of updating the original.That PR also used
immich-server
, so I'm not sure in @NLZ has a different docker setup to mine that changes thecontainer_name
directive to use-
instead of_
, but mine definitely createsimmich_server
:I updated the date on the original config to draw attention to this.
Also, I found a small typo in the CONTRIBUTING.md
Benefits of this PR and context
This requires less setup for users with immich, which means less chance of mistakes.
How Has This Been Tested?
I'm running this config locally in my SWAG instance without issues.
Source / References
The original official docker-compose never had
immich
as the service name, I suspect that the original SWAG config came from a community based template: https://github.com/immich-app/immich/blame/7cc7fc0a0c974e907702e0887b48312d3dd0a2b4/server/docker-compose.ymlI couldn't find any details in the wiki history either for the old name.