Skip to content

[Proposal] Ability to customize maintenance page #1532

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

Closed

Conversation

melya
Copy link

@melya melya commented Nov 13, 2020

Nobody wants their service to be down, but when it happens, we want to make it in a more "happier" 🌈 way

Let's say instead of rendering
Screen Shot 2020-11-13 at 7 03 31 PM

We could render some human readable page, like
Screen Shot 2020-11-13 at 7 02 40 PM

P.S. _This is just a proposal.
I did a quick test and it works.

Would be great to here any feedback if it's relevant_

location @maintenance {
error_page 405 = /index.html;
add_header Cache-Control no-cache;
root /usr/share/nginx/html/maintenance;
Copy link
Author

Choose a reason for hiding this comment

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

Maybe one page is enough and root is redundant.
Had thoughts if somebody needs a place for css

Choose a reason for hiding this comment

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

Thanks! I really need it, and wait for merge it!

@buchdag buchdag added status/pr-needs-tests This PR needs new or additional test(s) status/pr-needs-docs This PR needs new or additional documentation type/feat PR for a new feature labels Feb 25, 2022
@buchdag
Copy link
Member

buchdag commented May 2, 2024

Superseded by #2430, comments are welcome.

@buchdag buchdag closed this May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/pr-needs-docs This PR needs new or additional documentation status/pr-needs-tests This PR needs new or additional test(s) type/feat PR for a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants