Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates nginx to 3.5.8 and disables rate limiting #698

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

wisyhambolu
Copy link
Contributor

@wisyhambolu wisyhambolu commented Jun 14, 2024

TESTS ON LOCAL USING docker-wordpress-nginx 3.5.8

wisdomhambolu@Wisdoms-MacBook-Pro-2 test-root % echo $ALTIS_PACKAGE
altis/cms

wisdomhambolu@Wisdoms-MacBook-Pro-2 test-root % composer dev-tools codecept run -p vendor/$ALTIS_PACKAGE/tests
Running 1 suite(s), (acceptance)..
Flushing the cache...
Running "acceptance" test suite..

What's next?
  Try Docker Debug for seamless, persistent debugging tools in any container or image → docker debug test-root-db
  Learn more at https://docs.docker.com/go/debug-cli/
Starting headless "chrome" browser container..
7da7896316b616033ed25f1e53cc8d52c6d133ed5c05625ec5c5879ea96735af
Running Codeception..
Codeception PHP Testing Framework v4.2.2 https://helpukrainewin.org
Powered by PHPUnit 9.6.19 by Sebastian Bergmann and contributors.

Acceptance Tests (2) ---------------------------------------
✔ SignupsCest: Test I want to manage my network signups. (12.56s)
✔ SiteCest: Test I want to manage my network sites. (29.24s)
------------------------------------------------------------


Time: 01:14.607, Memory: 22.00 MB

OK (2 tests, 3 assertions)
Flushing the cache...
Removing test databases..

What's next?
  Try Docker Debug for seamless, persistent debugging tools in any container or image → docker debug test-root-db
  Learn more at https://docs.docker.com/go/debug-cli/
Removing headless browser container..

@hm-backport
Copy link

hm-backport bot commented Jun 14, 2024

The backport to v16-branch failed:

Commits ["719721b03943af62fce2f97159152ec529cadc3b"] could not be cherry-picked on top of v16-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v16-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick 719721b03943af62fce2f97159152ec529cadc3b
# Create a new branch with these backported commits.
git checkout -b backport-698-to-v16-branch
# Push it to GitHub.
git push --set-upstream origin backport-698-to-v16-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v16-branch and the compare/head branch is backport-698-to-v16-branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants