fix(docker): replace auth_storage named volume with bind mount

[marcelogorutuba]

Summary

• Substitui o named volume auth_storage por bind mount ./evo-auth-service-community/storage:/rails/storage no docker-compose.yml
• Remove a entrada auth_storage: da seção global de volumes

Problema

O named volume Docker era criado com ownership root, mas o processo Rails roda como usuário rails (UID 1000). Ao tentar salvar uma foto de perfil, o Rails tentava criar subpastas em /rails/storage/ e recebia Errno::EACCES: Permission denied @ dir_s_mkdir, retornando HTTP 500.

Solução

Com o bind mount, o Docker Desktop mapeia o diretório do host (./evo-auth-service-community/storage) com permissões de escrita para o processo do container, eliminando o erro de permissão.

Test plan

• Subir o serviço com docker compose up -d evo-auth
• Acessar perfil de usuário e fazer upload de nova foto
• Verificar que o avatar é salvo e exibido corretamente sem erros 500

🤖 Generated with Claude Code

Summary by Sourcery

Bug Fixes:

• Map the evo-auth service storage directory with a bind mount so the Rails process can write to /rails/storage inside the container.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the evo-auth service container configuration to mount the Rails storage directory from the host via a bind mount instead of using a Docker named volume, resolving file permission issues when Rails writes to /rails/storage.

Flow diagram for avatar upload using bind mounted storage

flowchart TD
    User["User uploads avatar via web UI"] --> AppServer["Rails app in evo-auth container"]
    AppServer --> ChoosePath["Write file to /rails/storage"]
    ChoosePath --> ContainerFS["Container path /rails/storage (bind mount)"]
    ContainerFS --> HostDir["Host directory ./evo-auth-service-community/storage"]
    HostDir --> Success["File saved successfully (no permission error)"]

Loading

File-Level Changes

Change	Details	Files
Switch Rails storage in evo-auth service from a Docker named volume to a host bind mount to fix permission errors.	Add a volumes section to the evo-auth service mapping ./evo-auth-service-community/storage to /rails/storage inside the container Rely on host directory permissions so the Rails process (UID 1000) can write to /rails/storage without Errno::EACCES errors Implicitly deprecate/remove the previous auth_storage named volume usage for this service	docker-compose.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Switching from a named volume to a relative bind mount hard-codes the repo layout (./evo-auth-service-community/storage); consider making the host path configurable (e.g., via an env var or a top-level x- anchor) or using a path that is stable even if the service directory is renamed.
• If this docker-compose.yml is used beyond local development, a bind mount to a project-relative directory may not exist or be writable in other environments; consider keeping the named volume for non-dev or moving this change into a dev-only override file.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Switching from a named volume to a relative bind mount hard-codes the repo layout (`./evo-auth-service-community/storage`); consider making the host path configurable (e.g., via an env var or a top-level `x-` anchor) or using a path that is stable even if the service directory is renamed.
- If this `docker-compose.yml` is used beyond local development, a bind mount to a project-relative directory may not exist or be writable in other environments; consider keeping the named volume for non-dev or moving this change into a dev-only override file.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}