Overall this is a great post, and yes knowing more about the bigger picture when doing front-end dev work can be very nice. It also fills in some of the mystery as far as how things are really working.
Couple of corrections: TXT records are not assigning your domain to a host, they are for outside resources, usually to confirm your domains ownership. Like for SEO, you can confirm your ownership of a domain with Google’s search console using a DNS TXT record—among other verification options. Otherwise, you’ll always be using A-records and CNAME records, and primarily A-records when hosting through a VPS.
SSL is certainly not “forced” unless you’ve got a text input on your site. Static sites for portfolios would be fine without SSL and won’t trigger the warning.
But, hey welcome to the world known as “devops”! It’s a frustratingly poorly documented and overly complex section of the development world that sadly isn’t usually taught as part of the typical path pf web development.
As a 12 year veteran of IT infrastructure, I would always recommend learning this portion after becoming comfortable with whatever regular development language/process you will use for your career. It’s helpful knowledge, but not required knowledge.
So on your infrastructure learning path, have you done anything to learn about load balancers, proxy protocols and how they effect things like the request and session headers? Or have you learned anything about the different methods for creating an app cluster vs a single node? It’s the logical next step, and absolutely excellent knowledge for when you’re freelancing and have a client with a site that’s growing to a respectable demand size.
Do you need any good resources on learning more about infrastructure? I’m happy to help and I’ve been looking for topics to help jr devs get more comfortable with DevOps.
Overall this is a great post, and yes knowing more about the bigger picture when doing front-end dev work can be very nice. It also fills in some of the mystery as far as how things are really working.
Couple of corrections: TXT records are not assigning your domain to a host, they are for outside resources, usually to confirm your domains ownership. Like for SEO, you can confirm your ownership of a domain with Google’s search console using a DNS TXT record—among other verification options. Otherwise, you’ll always be using A-records and CNAME records, and primarily A-records when hosting through a VPS.
SSL is certainly not “forced” unless you’ve got a text input on your site. Static sites for portfolios would be fine without SSL and won’t trigger the warning.
But, hey welcome to the world known as “devops”! It’s a frustratingly poorly documented and overly complex section of the development world that sadly isn’t usually taught as part of the typical path pf web development.
As a 12 year veteran of IT infrastructure, I would always recommend learning this portion after becoming comfortable with whatever regular development language/process you will use for your career. It’s helpful knowledge, but not required knowledge.
So on your infrastructure learning path, have you done anything to learn about load balancers, proxy protocols and how they effect things like the request and session headers? Or have you learned anything about the different methods for creating an app cluster vs a single node? It’s the logical next step, and absolutely excellent knowledge for when you’re freelancing and have a client with a site that’s growing to a respectable demand size.
Yes, agreed the TXT record mention was contextual. I will correct
Glad I could help.
Do you need any good resources on learning more about infrastructure? I’m happy to help and I’ve been looking for topics to help jr devs get more comfortable with DevOps.
Thank you, I'll be in touch.