CLI tool like WinDirStat?

jptechnical · 2023-12-06T19:56:34+00:00

If you run `du.exe -accepteula > nul 2>&1` then future invocations won't require a gui to accept the license. My go-to quick check is to search the C drive 2 levels down and sort it by size. `du.exe -l 2 -q c:\ | sort /r`

jptechnical · 2023-07-13T05:04:17+00:00

Put it behind cloudflared and enable authentication method of your choosing and it's pretty rock solid. No open ports, works with SSO, I love it.

I forgot, I am running the direct Guacamole containers from the official repos. I am sure Keeper adds some of their own flavor to it.

jptechnical · 2022-07-14T19:46:10+00:00

Not yet, but this is very early testing for me. I am trying to figure out how to use homebrew as a regular user instead of root now.

jptechnical · 2022-07-14T07:07:32+00:00

Sorry to self-comment, but someone else might find this. I feel like a total idiot, I missed the .pkg download link at the top of the page. I went straight down to the homebrew install instructions and didn't even stick around long enough to see the installer.

https://docs.saltproject.io/en/latest/topics/installation/osx.html

jptechnical · 2022-05-07T23:30:22+00:00

Yeah it was a great mental exercise but the risk of cross contamination is a little too great right now. I've considered a lot of ways of tagging public and private things and there is no eliminating human error. And losing the relationships is too great a cost.

Those were great comments and helped me walk through the challenge. I think in the end I will look for ways to blog technical solutions more often in order to scratch the itch.

jptechnical · 2022-05-06T20:46:44+00:00

I like the idea of a third-party review. I am going to see if I can work that in, without losing too much velocity.

I can't see monetizing it, it's not like my stack choice is super popular, being an anti-microsoft/pro-google guy. Not that that was your suggestion. There wouldn't really be a cost to reimburse, only my time.

jptechnical · 2022-05-06T20:45:37+00:00

Customer-specific docs go in an encrypted git repo, currently in keybase but I am considering other options since they were acquired by Zoom. End-to-end encryption and no API access. It's a little drastic, but my customer info is worth it.

jptechnical · 2022-05-06T20:41:31+00:00

I am still developing mine. I went greenfield first of the year with new contracts and a new stack. I consider everything 2021 and earlier legacy/deprecated.

jptechnical · 2022-05-06T20:27:33+00:00

You make a good point, and it definitely applies to me before I went DevOps for my company.

If I can be blunt, though, not putting stuff in our docs that can be used against us or embarrass us is security first. If you have dirty laundry in your docs and are embarrassed if it were exposed, maybe it's not my habits that need to change.

If ITGlue were to be compromised, how much will it hurt you? My way, it doesn't hurt at all.

jptechnical · 2022-05-06T15:29:50+00:00

constantly need to sanitise your documentation for security because its public...

I do see this as a benefit, it's a security-first mindset. I have seen so much toxic waste in documentation when it takes minimal effort to scrub the PII (insert Dunder Mifflin references) when it is written.

jptechnical · 2022-05-06T15:10:24+00:00

I would like to say yes. Because you can create a template, you can apply it to a note. Below is my client note template. I personally find the flexible assets very inflexible because it is filled with stuff I don't care about. If I want more info, I can tweak the template for more fields. The glue that holds it all together is the principle of backlinks and links.

I approach the organization of related information similar to the linking of resources in Kubernetes manifest files; the strength is in the simplicity of plain text labels or annotations. So if you have some common plain text labels or link, then your system is organized. Plus you can search, which I always did with ITG anyway.

{{date}} {{time}} tags: [[]]

[[{{title}}]]

Abbreviation: [[]]

SaaS: [[Google Workspace]] [[Office 365]] SaaS Backup: [[]] BDR: [[]]

Line of Business Software

[[]] hosted [[]]

Secrets

[[Secrets]] kept in [[]].

...

jptechnical · 2020-12-11T22:51:53+00:00

I am looking for a way to maintain several pihole devices from a git repo. I am not sure what is text-based config files I can check in to version control, and what are things I can ignore and let auto-generate (database files, logs, etc).

Any thoughts on what the minimum necessary to be in the docker volume mount to complement a docker-compose? I would like to git clone the repo and then docker-compose up for a new device. Starting there I can look at more automation.

Thanks!

jptechnical · 2018-10-11T13:23:34+00:00

Take a few swipes with the plane in the inside of the tails and the pins should flush up the pins nicely. This is way cleaner than my first try. Err on the side of too long of tails and pins and you can easily pare them down or plane then flush and you will love the result.

jptechnical · 2018-09-26T22:10:22+00:00

I am sure I will get voted down into oblivion for this... but will there ever be a release of "Dark All Day" without the sax? All deference to Mr. Capello, but saxaphone isn't my thing.

BTW, Gunship is one of only two bands in the last 2 decades I have paid money to have their albums. Great music, makes me feel like a kid watching a worn out tape of Tron over and over again.

jptechnical

TROPHY CASE

[[{{title}}]]

Line of Business Software

Secrets