I'm trying to think how I would explain this process to a newer professional: "So what was the problem?" "OK so I named a new type of content for the site with numbers." "OK." "And that worked with Jekyll." "OK." "So I deployed." "OK." "And everything broke because Nginx." "Wat"
-
-
Show this thread
-
"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 -
-
-
Just use a static site generator, they said. It will be easy, they said. ;)
- 3 more replies
New conversation -
-
-
They... don't, usually. I've seen a lot of people drown. The very first thing I teach people trying to get into programming / web development / etc. nowadays is "start with nothing, ignore all of the tools until you understand why and where you need them".
-
Same thing I tell people with OS , probably the same start everyone needs for any of the tech industry. Fortunately, there's no "Kali Linux" equivalent for web dev..... .....hopefully?
- 1 more reply
New conversation -
-
-
Pro tip:
@github pages make this so easy. Literally git push your Jekyll site and go. -
Unless you want a www prefix for your website and also https.
- 4 more replies
New conversation -
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.