Posts

So you just setup a new shiny WordPress website on a Lightsail (WordPress) instance. Now, you’ve been told to setup an SSL certificate for your website domain. What to do? The following steps show how to generate a free SSL certificate provided by Let’s Encrypt. bitnami@ip-172-26-12-25:~$ sudo /opt/bitnami/bncert-tool ---------------------------------------------------------------------------- Welcome to the Bitnami HTTPS Configuration tool. ---------------------------------------------------------------------------- Domains Please provide a valid space-separated list of domains for which you wish to configure your web server. Domain list []: lightsail.example.com The following domains were not included: www.lightsail.example.com. Do you want to add them? [Y/n]: n Warning: No www domains (e.g. www.example.com) or non-www domains (e.g. www.example.com) have been provided, so the following redirections will be disabled: non-www to www, www to non-www. Press [Enter] to continue: ---------------------------------------------------------------------------- Enable/disable redirections Please select the redirections you wish to enable or disable on your Bitnami installation. Enable HTTP to HTTPS redirection [Y/n]: Y ---------------------------------------------------------------------------- Changes to perform The following changes will be performed to your Bitnami installation: 1. Stop web server 2. Configure web server to use a free Let's Encrypt certificate for the domains: lightsail.example.com 3. Configure a cron job to automatically renew the certificate each month 4. Configure web server name to: lightsail.example.com 5. Enable HTTP to HTTPS redirection (example: redirect http://lightsail.example.com to https://lightsail.example.com) 6. Start web server once all changes have been performed Do you agree to these changes? [Y/n]: Y ---------------------------------------------------------------------------- Create a free HTTPS certificate with Let's Encrypt Please provide a valid e-mail address for which to associate your Let's Encrypt certificate. Domain list: lightsail.example.com Server name: lightsail.example.com E-mail address []: validemail@example.com The Let's Encrypt Subscriber Agreement can be found at: https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf Do you agree to the Let's Encrypt Subscriber Agreement? [Y/n]: ---------------------------------------------------------------------------- Performing changes to your installation The Bitnami HTTPS Configuration Tool will perform any necessary actions to your Bitnami installation. This may take some time, please be patient. ---------------------------------------------------------------------------- Success The Bitnami HTTPS Configuration Tool succeeded in modifying your installation. The configuration report is shown below. Backup files: * /opt/bitnami/apache/conf/httpd.conf.back.202405220509 * /opt/bitnami/apache/conf/bitnami/bitnami.conf.back.202405220509 * /opt/bitnami/apache/conf/bitnami/bitnami-ssl.conf.back.202405220509 * /opt/bitnami/apache/conf/vhosts/wordpress-https-vhost.conf.back.202405220509 * /opt/bitnami/apache/conf/vhosts/wordpress-vhost.conf.back.202405220509 Find more details in the log file: /tmp/bncert-202405220509.log If you find any issues, please check Bitnami Support forums at: https://github.com/bitnami/vms Press [Enter] to continue: That’s it. ...

I’m in the process of migrating existing Neovim plugins managed by Packer to a new plugin manager called ‘Lazy’. While setting the nvim-treesitter plugin, I came across this issue that nvim-treesitter keeps reinstalling all language parsers every time Neovim is started. [nvim-treesitter] [5/5] Treesitter parse for vim has been installed What happened? Well, it turns out this is is pretty much a common issue when you switching from Packer to Lazy plugin manager without cleaning up files and directories created by Packer according to this [1]. ...

On a few of my computers with 4K monitors running Linux, Firefox either display with tiny fonts or very large fonts, while most applications behave normally. After searching for a work around, I found the following solution works for me: setting the layout.css.devPixelsPerPx to a smaller number, e.g. 0.7. From this this page: You can set layout.css.devPixelsPerPx to 1.0 (default is -1) on the about:config page. Adjust its value in 0.1 or 0.05 steps (1.1 to enlarge or 0.9 to reduce) until icons or text looks right. You may need values above 2.0 if you have a high resolution display but make sure not to use values too large or too small. ...

Tonight I just stumbled on a command line tool or utility called ipcacl. This tool is used to perform operations on IP addresses and networks. On Fedora, ipcalc is provided by ipcacl package. If you on a different distro, search for ipcaclc, there should be a similar package name. ➜ rpm -q ipcalc ipcalc-1.0.3-9.fc40.x86_64 Here are some examples of what we can use this utility for, though I encourage you to run man ipcalc to learn more what you can do with it. ...

This is a short note on how to install metrics-server using Helm on my k8s cluster. $ kubectl version Client Version: v1.29.3 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.3 $ helm version --short v3.14.4+g81c902a Before we can install the chart, we will need to add the metrics-server repo to Helm. $ helm repo add metrics-server https://kubernetes-sigs.github.io/metrics-server/ Update the repo: $ helm repo update Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "metrics-server" chart repository Update Complete. ⎈Happy Helming!⎈ I also need to make a small customization to the chart’s default value since my k8s cluster uses self-signed certificates. ...