docker-compose exec -T <mongodb_service_name> mongodump --archive --gzip --db <mongodb_database> > dump.gz
docker-compose exec -T mongorestore --archive --gzip < dump.gz
| # For recent versions of Ubuntu: | |
| - https://www.pugetsystems.com/labs/hpc/ubuntu-22-04-server-autoinstall-iso/ | |
| # Docs: | |
| - https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls | |
| - https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigReference | |
| - https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html | |
| - https://discourse.ubuntu.com/t/please-test-autoinstalls-for-20-04/15250/53 | |
| # Download ISO Installer: |
| vm.max_map_count=262144 | |
| net.core.default_qdisc = fq | |
| net.ipv4.tcp_congestion_control = bbr | |
| net.ipv4.tcp_notsent_lowat = 16384 | |
| net.core.somaxconn = 4096 | |
| # Increase size of file handles and inode cache | |
| fs.file-max = 20971520 | |
| # Do less swapping |
| # TiMOS-B-14.0.R4 both/i386 Nokia 7750 SR Copyright (c) 2000-2016 Nokia. | |
| # All rights reserved. All use subject to applicable license agreements. | |
| # Built on Thu Jul 28 17:26:53 PDT 2016 by builder in /rel14.0/b1/R4/panos/main | |
| # Generated SUN MAR 13 06:28:52 2016 UTC | |
| exit all | |
| configure | |
| #-------------------------------------------------- | |
| echo "System Configuration" |
| #reference https://medium.com/@siriphonnot/backup-and-restore-a-mysql-database-from-a-running-docker-mysql-container-6c932907e21f | |
| #reference https://medium.com/@vineetcic/script-to-take-mysql-database-backup-for-last-7-days-45f97ed067a9 | |
| mysqlUser="root" | |
| mysqlPassword="xxxxx" | |
| mysqlHost="127.0.0.1" | |
| DB="my_db" | |
| credentialsFile="/mysql-credentials.cnf" | |
| /usr/local/bin/docker-compose exec -T mysql bash -c " |
I've spent the day trying to get this setup working with GitHub and given the number of gotcha's I encountered, it seemed like a good idea to document how I finally got this working with as few hacks as possible. There's a lot of documentation out there (some of it old and misleading) and committing here for posterity will help me remember this when I inevitably need to do this again.
Passwords are simply not enough these days. Regardless of the company, breaches (and the associated Personally Identifiable Information harvested) are a matter of not if, but when. There are a number of things you can do to protect yourself, but being on the tin-foil-hat side of paranoia, means there are a few Commandents that I adhere to (and recommend for other folks)[Insert link to Fight Club Rules for the Secure Internet].
That being said, if you use 2-factor authentication and have committed to using a hardware token such as the Yubikey, then you're already ahead of the curve. The problem is that wh
| #!/bin/bash | |
| # Parallel rsync script originally designed for rsyncing | |
| # large ata transfers from RAID to RAID for the Aagaard Lab. | |
| # Author: Michael Jochum | |
| # Location: Baylor College of Medicine, Houston, TX, USA | |
| # Contact : michael.jochum@bcm.edu | |
| # Date : 2 November 2020 | |
| ################################## | |
| #Step 0: fill this shit out |
Here is the best setup (I think so :D) for K-series Keychron keyboards on Linux.
Note: many newer Keychron keyboards use QMK as firmware and most tips here do not apply to them. Maybe the ones related to Bluetooth can be useful, but everything related to Apple's keyboard module (hid_apple) on Linux, won't work. As far as I know, all QMK-based boards use the hid_generic module instead. Examples of QMK-based boards are: Q, Q-Pro, V, K-Pro, etc.
Most of these commands have been tested on Ubuntu 20.04 and should also work on most Debian-based distributions. If a command happens not to work for you, take a look in the comment section.
Older Keychron keyboards (those not based on QMK) use the hid_apple driver on Linux, even in the Windows/Android mode, both in Bluetooth and Wired modes.
The go command line tool needs to be able to fetch dependencies from your private GitLab, but authenticaiton is required.
This assumes your private GitLab is hosted at privategitlab.company.com.
The following environment variables are recommended:
export GO111MODULE=on
export GOPRIVATE=privategitlab.company.comThe first half of this table lists base images for execution environments (EE).
| Quay page ( ansible/*) |
Tag | Repository ( ansible/*) |
Default branch |
|---|---|---|---|
quay.io/centos/centos:8 |
main |
||
| python-base | quay.io/ansible/python-base:latest |