Good thing Google makes creating/tearing down containers is easy. It actually took like, 4 tries to get it right.
Why do SSL?
My plan is to eventually do E-Commerse through wordpress. Security is mandatory if you want to be trusted. See this little lock bar?
Not having that is a death sentence because anyone intercepting requests between us(You the reader and the server this site is on) is not securely encrypted.
Google doesn’t exactly make it easy to ensure your site is SSL secure like a lot of the other WordPress specific hosting sites. I don’t come from a networking or security background so I don’t really care how it works behind the scenes. It took me 4 tries to get it all right and the way I wanted it set up.
I initially tried using Google’s One Click deploy but it’s basically all up to you in order to generate the SSL cert. I found out the application packaging company Bitnami just did WordPress way better… and since I wanted the multi site feature. I used
Since the main one use GCE, I’m trying to set it up within their free tier.
In order to use Bitnami’s script, you need a static IP (Google offers a way to convert ephemeral to static IPs on the UI) and also set up the DNS to your website. Since I use google domains, I just transferred it to Cloud DNS.
Here’s how you use the script
The downside of the script is that it doesn’t let you create wildcarded SSL certs, so you basically need to create it for your main domain. I’d prefer wildcard so that I could set up WordPress like
and use a cert for any *.filnguyen.com site. They didn’t allow that so I made a workaround by having sites separated by subdirectories instead
I’m assuming I can have a separate domain and map filnguyen.com/site1 to a different domain. That’s a TODO but setting it up like this means any site under filnguyen.com will be SSL secured. The guide I followed to use subdirectories can be found here.
Those are my notes. Maybe I’ll create an actual guide or something later.