Skip to content

We do support nginx+php-fpm these days!#14138

Merged
szaimen merged 1 commit intomasterfrom
nginx-supported
Mar 19, 2026
Merged

We do support nginx+php-fpm these days!#14138
szaimen merged 1 commit intomasterfrom
nginx-supported

Conversation

@pabzm
Copy link
Copy Markdown
Member

@pabzm pabzm commented Mar 19, 2026

☑️ Resolves

Until now there was a note that NGINX wouldn't be supported officially, even though we do support it since a while. This is not changed, including a clear statement of support (just removing the note could be confusing to users/customers).

🖼️ Screenshots

image

Signed-off-by: Pablo Zmdl <pablo@nextcloud.com>
Copy link
Copy Markdown
Member

@provokateurin provokateurin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙈

Copy link
Copy Markdown
Contributor

@szaimen szaimen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks! :)

@szaimen szaimen added this to the Nextcloud 34 milestone Mar 19, 2026
@szaimen szaimen merged commit 56a051e into master Mar 19, 2026
12 checks passed
@szaimen szaimen deleted the nginx-supported branch March 19, 2026 09:43
@szaimen
Copy link
Copy Markdown
Contributor

szaimen commented Mar 19, 2026

/backport to stable33

@szaimen
Copy link
Copy Markdown
Contributor

szaimen commented Mar 19, 2026

/backport to stable32

@backportbot
Copy link
Copy Markdown

backportbot bot commented Mar 19, 2026

The backport to stable32 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable32
git pull origin stable32

# Create the new backport branch
git checkout -b backport/14138/stable32

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick a24b9ccf

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/14138/stable32

Error: Failed to check for changes with origin/stable32: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@szaimen
Copy link
Copy Markdown
Contributor

szaimen commented Mar 19, 2026

/backport to stable32

@backportbot
Copy link
Copy Markdown

backportbot bot commented Mar 19, 2026

The backport to stable32 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable32
git pull origin stable32

# Create the new backport branch
git checkout -b backport/14138/stable32

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick a24b9ccf

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/14138/stable32

Error: Failed to check for changes with origin/stable32: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@szaimen
Copy link
Copy Markdown
Contributor

szaimen commented Mar 19, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 3, 2026

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

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