"/dev/nvme0n1p1" => /boot/efi (fat32)
"/dev/nvme0n1p2" => /boot (ext4)
"/dev/nvme0n1p3/" => / (f2fs)
| # Client configs, 16.04, | |
| script-security 2 | |
| up /etc/openvpn/update-resolv-conf | |
| down /etc/openvpn/update-resolv-conf | |
| # network manager, 16.04, install below package to enable import openvpn client configs | |
| sudo apt install network-manager-openvpn-gnome | |
| # Client configs, 18.04/18.10 |
| #!/bin/bash | |
| # This script cleans all cache for Microsoft Teams on Linux | |
| # Tested on Ubuntu-like, Debian by @necrifede, Arch Linux by @lucas-dclrcq and Manjaro with flatpak by @danie1k. Feel free to test/use in other distributions. | |
| # Tested Teams via snap package. | |
| # Tested Teams via flatpak package. | |
| # | |
| # How to use in terminal: | |
| # ./clear_cache_MS_Teams.sh ( deb-stable | deb-insider | snap | flatpak ) | |
| # or |
It happened after secrets file was lost during GitLab upgrade.
The case described in documentation When the secrets file is lost
But not completely clear.
From log file /var/log/gitlab/gitlab-rails/production.log:
| br-ex IP address is 172.24.4.1/24 | |
| iptables -I FORWARD -i br-ex -j ACCEPT | |
| iptables -I FORWARD -o br-ex -j ACCEPT | |
| iptables -t nat -I POSTROUTING -s 172.24.4.0/24 ! -d 172.24.4.0/24 -j MASQUERADE |
| // Related to https://issues.jenkins-ci.org/browse/JENKINS-26481 | |
| abcs = ['a', 'b', 'c'] | |
| node('master') { | |
| stage('Test 1: loop of echo statements') { | |
| echo_all(abcs) | |
| } | |
| stage('Test 2: loop of sh commands') { |
| def flatten_json(json): | |
| if type(json) == dict: | |
| for k, v in list(json.items()): | |
| if type(v) == dict: | |
| flatten_json(v) | |
| json.pop(k) | |
| for k2, v2 in v.items(): | |
| json[k+"."+k2] = v2 | |
– Filtering AWS resources with Boto3
This post will be updated frequently when as I learn more about how to filter AWS resources using Boto3 library.
Filtering VPCs by tags
Services declared as oneshot are expected to take some action and exit immediatelly (thus, they are not really services,
no running processes remain). A common pattern for these type of service is to be defined by a setup and a teardown action.
Let's create a example foo service that when started creates a file, and when stopped it deletes it.
Create executable file /opt/foo/setup-foo.sh: