15 years of being a professional software engineer: can *almost* publish static HTML to my blog with the same likelihood as HTTP 200 that I had when doing my Warcraft 2 fan site in middle school on AOL. *Almost.* (Freaking toolchains.) How do folks learning now survive?!
-
-
"Yeah that sometimes happens." "So what did you do?" "Oh I changed the template for my configuration file to add a regular expression specifying try_files for a particular subdirectory and then rebooted the server. You know, as one does." "And that worked?" "Not the first time."
Show this thread -
"What happened the first time?" "Well the files that were 404ing started 200ing but the files which were 200ing started 500ing." "That means?" "That's bad." "OK." "So I tried another thing and it fixed that but it broke the HTTP version of my site because of a tooling issue."
Show this thread -
"The HTTP version?" "Yes; the insecure one." "You have an insecure one." "Yes good you're paying attention." "Why do you have an insecure one?" "To point people to the secure one." "Can you not have that?" "Well theoretically if you set the right headers but SEO concerns mean..."
Show this thread
End of conversation
New conversation -
-
-
I have to ask, why do you need these tools when SCP/SFTP works just fine? Serious question. Either people have forgotten how easy it is to do it properly, or I am missing something (yet my site works just fine).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I can help next time! ;)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
After way too many problems with Jekyll, I threw it under the bus and switched to Hugo, much happier. Many problems still, but, fewer.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.