Ryan Rosado

Let's say we have a hosting service for users who bring their own domain name. In this scenario we'd like to be able to service customers no matter who manages their DNS records. Be it GoDaddy, Namecheap, Google, Hostgator, some offshore place, etc.

At the same time, we'd also like to provide Load balancing so no one-user can overload any of our systems. This means, instead of having a customer's domain name point directly to the system where their webserver or app resides, it will point the HTTP connection to a Load Balancer which is prepared to handle serious connection

It's Sunday and you know what that means... time to catch up on work outside of work.

I recently used LetsEncrypt for the awesome temporary free SSL Certs they offer. In the last use I became familiar with and implemented the use of certbot.

I did not go so far as to automate certbot to check for and update near-expiring certs. But this is coming up soon...

However, it's come time to renew so I've had to reteach myself how to do it, grasping for all logs in 'history' over a few different machines, I was able to easily re-do

Hello and Welcome, this is the first installment of "Weekend Worker" series.

Today as a Weekend Worker i'll be implementing an automatic backup system to backup each individual client website.

We'll be using the following technologies:

• Linux cron job
• Bash
• Ansible
• Docker
• AWS ECS
• VNC server

And we'll setup our dev environment on our home Windows desktop with the following tools:

• Ansible for Windows (to launch dev tests)
• Visual Studio Code (for editing and pushing updates)
• Git (so our remote prod server can grab the code updates)
• VNCviewer (to access prod remotely)
• Bitbucket (for source control)

Preparing the