Fix nginx: remove must-revalidate from gzip_proxied to prevent startu…

[DaniloGouvea]

Pull Request

📋 Description

Invalid value "must-revalidate" in /etc/nginx/conf.d/nginx.conf preventing evolution manager v2 startup locally.

Line changed from:
gzip_proxied expired no-cache no-store private must-revalidate auth;

To:
gzip_proxied expired no-cache no-store private auth;

The container now starts correctly.

The nginx documentation supports the change (http://nginx.org/en/docs/http/ngx_http_gzip_module.html#gzip_proxied):

Syntax: gzip_proxied off | expired | no-cache | no-store | private | no_last_modified | no_etag | auth | any ...;
Default: gzip_proxied off;
Context: http, server, location

🔗 Related Issues

N/A

• Fixes #

🧪 Type of Change

• [ X ] 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Style/UI changes
• ♻️ Code refactoring (no functional changes)
• ⚡ Performance improvements
• 🔧 Build/CI changes
• 🧪 Tests

🧪 Testing

Test Environment

• Local development
• Staging environment
• Production-like environment

Test Cases

• Unit tests pass
• Integration tests pass
• Manual testing completed
• Cross-browser testing (if applicable)
• Mobile testing (if applicable)

Test Instructions

1. Pull the container image and run it on Docker:
   services:
   frontend:
   container_name: evolution_frontend
   image: evoapicloud/evolution-manager:latest
   restart: always
   ports:
   • "3000:80"
     networks:
   • evolution-net

📸 Screenshots

N/A

Before

N/A

After

N/A

✅ Checklist

Code Quality

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• [ ] I have run npm run lint and fixed any issues

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested the changes in multiple browsers (if applicable)
• I have tested the changes on mobile devices (if applicable)

Documentation

• I have made corresponding changes to the documentation
• I have updated the README.md if necessary
• I have added/updated JSDoc comments for new functions
• I have updated type definitions if necessary

Internationalization

• I have added translations for new text strings
• I have tested the changes in different languages (if applicable)

Breaking Changes

• This PR introduces breaking changes
• I have documented the breaking changes in the description
• I have updated the migration guide (if applicable)

🔄 Migration Guide

N/A

Before

// Old code example

After

// New code example

📝 Additional Notes

N/A

🤝 Reviewer Guidelines

Focus Areas

• Code logic and correctness
• Performance implications
• Security considerations
• User experience
• Accessibility
• Browser compatibility

Testing Checklist for Reviewers

• Pull and test the branch locally
• Verify the fix/feature works as described
• Check for edge cases
• Verify no regressions in existing functionality

---

Thank you for contributing to Evolution Manager! 🚀

Summary by Sourcery

Bug Fixes:

• Remove invalid "must-revalidate" value from gzip_proxied in nginx.conf to allow the container to start correctly

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Remove invalid 'must-revalidate' directive from nginx gzip_proxied settings to restore container startup and compliance with nginx documentation.

Flow diagram for nginx startup with corrected gzip_proxied settings

flowchart TD
  A["nginx.conf with invalid 'must-revalidate'"] --> B["nginx startup fails"]
  C["nginx.conf with valid settings (without 'must-revalidate')"] --> D["nginx startup succeeds"]

Loading

File-Level Changes

Change	Details	Files
Eliminate unsupported 'must-revalidate' token from gzip_proxied directive	Deleted 'must-revalidate' option from the gzip_proxied configuration Added trailing newline at end of file	.docker/nginx.conf

---

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 there - I've reviewed your changes and they look great!

---

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