docs: narzedzie na stronie, przez ktora wchodzi caly serwis - #247
Merged
Merged
Conversation
Checked rather than assumed, and the result was worse than expected: the docs homepage mentioned zerosmtp-check zero times, npx zero times, and linked to none of the seventeen per-error pages. It is the entry point for the site and it knew nothing about two days of work. Same failure as the orphan pages and the README earlier today, in a third place: the thing gets built and does not appear where people land. It goes above the triage table rather than becoming a seventeenth row in it. The table answers "which page do I need", which is the right question when you are reading. Somebody mid-incident with an error on screen has a different one, and for them a single command beats picking from sixteen options - especially since the string they are looking at is usually not what the server sent, which is the part no page can tell them by being well organised. The hanging case is named separately because it is the most common first failure and it is not an authentication problem at all: the network is refusing the port, and no amount of reading about 5.7.139 will say so.
This file contains hidden or 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
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.
Sprawdzone, nie założone — i wynik gorszy, niż się spodziewałem:
zerosmtp-checknpxTo punkt wejścia całego serwisu i nie wiedział nic o dwóch dniach pracy.
Ta sama wada co sieroty i README dziś rano, w trzecim miejscu: rzecz zostaje zbudowana i nie pojawia się tam, gdzie ludzie lądują.
Nad tabelą, nie jako jej siedemnasty wiersz
Tabela odpowiada na pytanie „której strony potrzebuję" — słuszne, gdy ktoś czyta. Ktoś w trakcie awarii, z błędem na ekranie, ma inne pytanie, i dla niego jedna komenda bije wybór z szesnastu opcji. Zwłaszcza że tekst, na który patrzy, zwykle nie jest tym, co wysłał serwer — a tego żadna strona nie powie mu przez dobrą organizację.
Przypadek zawieszania nazwany osobno, bo to najczęstsza pierwsza awaria i w ogóle nie jest problemem uwierzytelniania: sieć odrzuca port, a żadna ilość czytania o
5.7.139tego nie powie.