Create a BUSY landing page #947
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* `BUSY_LAG` environment var so this can be twiddled with later * `FORCE_BUSY` environment var to indicate technical difficulties with styling * `FORCE_BUSY_ABSOLUTE` environment var to indicate technical difficulties with no UI * Change the messages to suit **NOTE** This is also to test to see where the memory leak is happening... *mu2* isn't leaking since the hard-coded 503 has been in place and the average memory usage is around ~6% Applies to OpenUserJS#944, OpenUserJS#249 and OpenUserJS#37
Martii
added
enhancement
pull bot
pushed a commit
to Patreos998/OpenUserJS.org
that referenced
this pull request
Jul 17, 2024
* Give a custom message. Will be needing this on an upcoming server migration. Letsencrypt hasn't ever been transferred to a new server and not sure how it will react... so keep us FORCEd BUSY. Post OpenUserJS#947 Auto-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BUSY_LAGenvironment var so this can be twiddled with laterFORCE_BUSYenvironment var to indicate technical difficulties with stylingFORCE_BUSY_ABSOLUTEenvironment var to indicate technical difficulties with no UI (e.g. response status only)NOTE
This is also to test to see where the memory leak is happening... mu2 isn't leaking since the hard-coded 503 has been in place and the average (peak) memory usage is around ~6%
Applies to #944, #249 and #37