fix(EVO-976): fix avatar storage — shared volumes, AUTH_SERVICE_URL, storage docs

[marcelogorutuba]

Resumo

Corrige os critérios de aceite pendentes do EVO-976 não endereçados no PR #41:
foto de perfil com 404, volumes de storage não compartilhados e documentação ausente.

Mudanças

docker-compose.yml

• Adiciona crm_storage volume declarado ao evo-crm e evo-crm-sidekiq
• Sem volume compartilhado, blobs escritos pelo Sidekiq ficavam invisíveis ao container web (root cause do issue original com ACTIVE_STORAGE_SERVICE=local)

.env.example

• Adiciona AUTH_SERVICE_URL=http://localhost:3001 — variável lida pelo auth service para montar URLs absolutas de avatar (ver PR chore(deps): bump actions/upload-artifact from 4.6.2 to 7.0.0 #10 em evo-auth-service-community)
• Expande seção de cloud storage com guia completo para Cloudflare R2 / AWS S3, incluindo nota sobre CORS do bucket (critério de aceite do issue que estava faltando)

evo-auth-service-community (bump para PR #10)

• avatarable.rb: rails_service_blob_proxy_path → URL absoluta com app_url
• environment_config.rb: lê AUTH_SERVICE_URL, configura routes.default_url_options
• development.rb: corrige action_mailer porta 3000 → 3001

Critérios de aceite × este PR

Critério	Status
Images persist to S3	✅ (PR anterior)
CORS / port mismatches resolved	✅ volume compartilhado + docs CORS bucket
Profile photo upload persists	✅ avatarable.rb URL absoluta
Storage env vars documentados no README	✅ .env.example expandido

Test plan

• docker-compose up → upload de imagem via WhatsApp → imagem visível na conversa após reload
• Upload de avatar no perfil → avatar persiste após reload (sem 404)
• ACTIVE_STORAGE_SERVICE=s3_compatible com R2 → avatar carrega direto do bucket
• .env.example cópia → AUTH_SERVICE_URL presente por padrão

🤖 Generated with Claude Code

Summary by Sourcery

Ensure avatar and storage behavior works correctly across services and environments

Enhancements:

• Share a persistent crm_storage volume between the evo-crm web and Sidekiq containers to keep uploaded files visible across processes
• Mount a storage volume for the auth service container and adjust its startup command to clear stale Rails PID files before booting the server

Documentation:

• Update environment example configuration to include AUTH_SERVICE_URL and expanded guidance for S3-compatible/cloud storage setup

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

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:

• Consider using a named volume for evo-auth-service-community storage instead of a host bind (./evo-auth-service-community/storage:/rails/storage) to keep storage handling consistent with the CRM services and avoid path-related discrepancies across environments.
• Since storage is now shared via crm_storage, it might be worth explicitly calling out any expected cleanup or migration for existing local blobs to avoid unexpected behavior for developers who already have non-shared storage data.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider using a named volume for `evo-auth-service-community` storage instead of a host bind (`./evo-auth-service-community/storage:/rails/storage`) to keep storage handling consistent with the CRM services and avoid path-related discrepancies across environments.
- Since storage is now shared via `crm_storage`, it might be worth explicitly calling out any expected cleanup or migration for existing local blobs to avoid unexpected behavior for developers who already have non-shared storage data.

---

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.}