yarnd will in fact spit warnings/errors in the logs when it encounters bad feeds (_this being an example_) π€£
yarnd will in fact spit warnings/errors in the logs when it encounters bad feeds (_this being an example_) π€£
refactor_twt_options branch. I am afraid that CSS is over my head. I am not giving up yet, but not getting too far.
> Whatβs this? π€ What are you up to?
I have my server spit out that custom error 502 when yarnd is down.
/user/.*/twtxt.txt myself with basically a custom feed that behaves like a Twtxt feed π€ This _could_ be interesting π€
/user/.*/twtxt.txt myself with basically a custom feed that behaves like a Twtxt feed π€ This _could_ be interesting π€
> custom 502 response for
/user/.*/twtxt.txt myself with basically a custom feed that behaves like a Twtxt feedIt is possible, but reading that made me re-live one of 'Rick and Morty' episodes. π€£
handle_errors {
rewrite * /twtxt.txt
file_server
}
And all errors will show that file. More on Caddy's error handling.
/user/*/twtxt.txt.
/user/*/twtxt.txt.
200 OK which means that my pod (_and all other pods_) would have suddenly seen his feed as "empty". It's for this reason I _think_ the following line of code needs to guard against if len(twts) > 0 ...
200 OK which means that my pod (_and all other pods_) would have suddenly seen his feed as "empty". It's for this reason I _think_ the following line of code needs to guard against if len(twts) > 0 ...