Tech

In order to test locally a Gemfile, define local path for the gems to avoid attempting to write to system-wide folders: bundle config set --local path '/home/username/.gem' bundle install

With recent releases of OpenShift like 4.13 you can use CoreOS Layering to apply custom images to the nodes. The feature allows to build, via a Dockerfile a custom image that can later be applied to our nodes. Let’s review the steps: First we need to find the base image being used in our environment with oc adm release info quay.io/openshift-release-dev/ocp-release:4.13.5-aarch64 --image-for=rhel-coreos Then we use the returned value in the FROM line in our Dockerfile If we want to add custom packages, we should have a server which is reachable and run createrepo on the folder containing the rpm’s so that rpm-ostree can download them for installation. Example dockerfile: ...

Hi had the chance to buy a Dlink camera, waterproof, with magnetic base and rated for exteriors for a really great price a while ago D-Link DCS 8600LH 🛒#ad and later a camera with pan and tilt from Dlink too D-Link DCS-6500LH 🛒#ad The camera, of course has an application for configuration, viewing the image, etc named ‘mydlink’ which has a web counterpart at https://mydlink.com/, but unfortunately, when you try to access the website, there’s little you can do: ...

As you might have experienced… using a recent system to connect to a legacy one could be complicated as some insecure protocols have been disabled, with a message like: Unable to negotiate with 192.168.2.82 port 22: no matching host key type found. Their offer: ssh-rsa,ssh-dss Create an entry like this in your .ssh/config file, so that insecure methods can be used to connect to a specific host: Host 192.168.2.82 HostKeyAlgorithms=+ssh-rsa KexAlgorithms=+diffie-hellman-group1-sha1 PubkeyAcceptedKeyTypes=+ssh-rsa User root or alternatively on the command line: ...

I had two Raspberry Pi systems running Raspbian and they were failing to find updates for newer packages. As Debian stable was upgraded too, moving from buster to bullseye the packages failed to get the newer ones. Warning Beware as this procedure might upgrade the system but might no render a bootable Raspberry Pi A way to fix it is, to first, change references, if any, to the old codename version by running: ...