| Welcome to StackOverflow! Your question is not quite clear. | |
| Perhaps its worth rephrasing it so that someone would be able to help you further. | |
| It is a great idea to refer to [this article](https://stackoverflow.com/help/how-to-ask) on how to ask a good question. Thanks. |
| yum install -y git libcgroup-tools |
| # Session 1 | |
| * Cargo new create a a ready to use git repository | |
| * Where does cargo gets the author information? | |
| If you have already set it for git you'd be OK. | |
| For additional options, Look up: https://github.com/rust-lang/cargo/blob/rust-1.50.0/src/cargo/ops/cargo_new.rs#L798 | |
| * |
| 1. Check what is the state - git remote -v | |
| 2. If the upstream is missing add it - git remote add upstream https://github.com/apache/camel | |
| 3. Fetch from upstream - git fetch upstream | |
| 4. Checkout local working copy master/main - git checkout master | |
| 5. Merge upstream master into local - git merge upstream/master | |
| 6. Push upstream - git push origin |
| What: Configure IntelliJ IDEA to use self-signed certificates for license servers | |
| Background: Current employer hasan IntelliJ license server hosted at https://intellij.employer.domain and uses a proxy with self-signed inspection proxy(Pretty much MITM) | |
| Solution: | |
| 1. Download the root CA, intermediate CA and inspection CA certificates from the employer's PKI registry | |
| 2. Go to `/Applications/IntelliJ\ IDEA.app/Contents/jbr/Contents/Home` (Tested for 2021.3 version) | |
| 3. Get an elevated prompt | |
| 4. Add root CA |
| GRPC_DEFAULT_SSL_ROOTS_FILE_PATH=/Users/foo/Downloads/inspection-ca.cer | |
| http_proxy=http://localhost:3128/ | |
| https_proxy=http://localhost:3128/ | |
| Additional variables for GRPC here: https://github.com/grpc/grpc/blob/master/doc/environment_variables.md |
Spotted this item on Ben Hutchingson's LinkedIN Feed. There may be IT's equivalent of LRQ worth looking into.
| # pihole.container | |
| # This is a podman quadlet file to run Pi-hole as a container | |
| # On my lab this runs in the context of a limited user account named `pihole` | |
| # This file goes to `/home/pihole/.config/containers/systemd/pihole.container` | |
| # | |
| # Here are the steps to set it up. Oh for sure there are other ways to get it done, but this is my way! | |
| # 0. Enable user lingering for the `pihole` user, if not already done: | |
| # sudo loginctl enable-linger pihole | |
| # 1. Open a shell as the `pihole` user: | |
| # sudo machinectl shell pihole@ |
| name | slo-coach | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| description | SLO coach for software engineering teams. Use when: defining SLIs/SLOs, choosing reliability targets, aligning error budgets with business needs, reviewing existing SLOs, connecting SLOs to SLAs, understanding what to measure. | |||||||||
| argument-hint | Describe your service and what reliability questions you have | |||||||||
| metadata |
|
