convert existing posts to pageBundles
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 44 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: Projects
|
||||
date: "2018-09-26T08:34:30Z"
|
||||
thumbnail: images/posts-2020/i0UKdXleC.png
|
||||
usePageBundles: false
|
||||
thumbnail: i0UKdXleC.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- docker
|
||||
- linux
|
||||
|
|
@ -10,7 +10,7 @@ tags:
|
|||
title: BitWarden password manager self-hosted on free Google Cloud instance
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
A friend mentioned the [BitWarden](https://bitwarden.com/) password manager to me yesterday and I had to confess that I'd never heard of it. I started researching it and was impressed by what I found: it's free, [open-source](https://github.com/bitwarden), feature-packed, fully cross-platform (with Windows/Linux/MacOS desktop clients, Android/iOS mobile apps, and browser extensions for Chrome/Firefox/Opera/Safari/Edge/etc), and even offers a self-hosted option.
|
||||
|
||||
|
Before Width: | Height: | Size: 552 KiB After Width: | Height: | Size: 552 KiB |
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 198 KiB After Width: | Height: | Size: 198 KiB |
|
Before Width: | Height: | Size: 1.3 MiB After Width: | Height: | Size: 1.3 MiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
date: "2020-09-14T08:34:30Z"
|
||||
thumbnail: /images/posts-2020/qDTXt1jp3.png
|
||||
featureImage: /images/posts-2020/qDTXt1jp3.png
|
||||
usePageBundles: false
|
||||
thumbnail: qDTXt1jp3.png
|
||||
featureImage: qDTXt1jp3.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- linux
|
||||
- chromeos
|
||||
|
|
@ -18,12 +18,12 @@ That's a pretty sweet setup, but I still needed a way to convert STL 3D models i
|
|||
Enter "Crostini," Chrome OS's [Linux (Beta) feature](https://chromium.googlesource.com/chromiumos/docs/+/master/containers_and_vms.md). It consists of a hardened Linux VM named `termina` which runs (by default) a Debian Buster LXD container named `penguin` (though you can spin up just about any container for which you can find an [image](https://us.images.linuxcontainers.org/)) and some fancy plumbing to let Chrome OS and Linux interact in specific clearly-defined ways. It's a brilliant balance between offering the flexibility of Linux while preserving Chrome OS's industry-leading security posture.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
There are plenty of great guides (like [this one](https://www.computerworld.com/article/3314739/linux-apps-on-chrome-os-an-easy-to-follow-guide.html)) on how to get started with Linux on Chrome OS so I won't rehash those steps here.
|
||||
|
||||
One additional step you will probably want to take is make sure that your Chromebook is configured to enable hyperthreading, as it may have [hyperthreading disabled by default](https://support.google.com/chromebook/answer/9340236). Just plug `chrome://flags/#scheduler-configuration` into Chrome's address bar, set it to `Enables Hyper-Threading on relevant CPUs`, and then click the button to restart your Chromebook. You'll thank me later.
|
||||
|
||||
|
||||
|
||||
### The Software
|
||||
I settled on using [FreeCAD](https://www.freecadweb.org/) for parametric modeling and [Ultimaker Cura](https://ultimaker.com/software/ultimaker-cura) for my GCODE slicer, but unfortunately getting them working cleanly wasn't entirely straightforward.
|
||||
|
|
@ -65,7 +65,7 @@ Comment[de_DE]=Feature-basierter parametrischer Modellierer
|
|||
MimeType=application/x-extension-fcstd
|
||||
```
|
||||
That's it! Get on with your 3D-modeling bad self.
|
||||
|
||||
|
||||
Now that you've got a model, be sure to [export it as an STL mesh](https://wiki.freecadweb.org/Export_to_STL_or_OBJ) so you can import it into your slicer.
|
||||
|
||||
#### Ultimaker Cura
|
||||
|
|
@ -85,12 +85,12 @@ $ sudo apt update && sudo apt install menulibre
|
|||
$ menulibre
|
||||
```
|
||||
Just plug in the relevant details (you can grab the appropriate icon [here](https://github.com/Ultimaker/Cura/blob/master/icons/cura-128.png)), hit the filing cabinet Save icon, and you should then be able to search for Cura from the Chrome OS launcher.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
From there, just import the STL mesh, configure the appropriate settings, slice, and save the resulting GCODE. You can then just upload the GCODE straight to The Spaghetti Detective and kick off the print.
|
||||
|
||||
|
||||
|
||||
|
||||
Nice!
|
||||
|
Before Width: | Height: | Size: 180 KiB After Width: | Height: | Size: 180 KiB |
|
Before Width: | Height: | Size: 664 KiB After Width: | Height: | Size: 664 KiB |
|
Before Width: | Height: | Size: 211 KiB After Width: | Height: | Size: 211 KiB |
|
Before Width: | Height: | Size: 173 KiB After Width: | Height: | Size: 173 KiB |
|
Before Width: | Height: | Size: 61 KiB After Width: | Height: | Size: 61 KiB |
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 52 KiB |
|
Before Width: | Height: | Size: 55 KiB After Width: | Height: | Size: 55 KiB |
|
Before Width: | Height: | Size: 228 KiB After Width: | Height: | Size: 228 KiB |
|
Before Width: | Height: | Size: 53 KiB After Width: | Height: | Size: 53 KiB |
|
Before Width: | Height: | Size: 347 KiB After Width: | Height: | Size: 347 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 52 KiB |
|
Before Width: | Height: | Size: 88 KiB After Width: | Height: | Size: 88 KiB |
|
Before Width: | Height: | Size: 218 KiB After Width: | Height: | Size: 218 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: Tips
|
||||
date: "2020-09-24T08:34:30Z"
|
||||
thumbnail: images/posts-2020/fmLDUWjia.png
|
||||
usePageBundles: false
|
||||
thumbnail: fmLDUWjia.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- chrome
|
||||
title: Abusing Chrome's Custom Search Engines for Fun and Profit
|
||||
|
|
@ -12,25 +12,25 @@ Do you (like me) find yourself frequently searching for information within the s
|
|||
|
||||
### The basics
|
||||
Point your browser to `chrome://settings/searchEngines` to see which sites are registered as Custom Search Engines:
|
||||
|
||||
|
||||
|
||||
Each of these search engine entries has three parts: a name ("Search engine"), a Keyword, and a Query URL. The "Search engine" title is just what will appear in the Omnibox when the search engine gets triggered, the Keyword is what you'll type in the Omnibox to trigger it, and the Query URL tells Chrome how to handle the search. All you have to do is type the keyword, hit your Tab key to activate the search, input your query, and hit Enter:
|
||||
|
||||
|
||||
|
||||
For sites which register themselves automatically, the keyword is often set to something like `domain.tld` so it might make sense to assign it as something shorter or more descriptive.
|
||||
|
||||
The Query URL is basically just what appears in the address bar when you search the site directly, with `%s` placed where your query text would normally go. You can view these details for a given search entry by tapping the three-dot menu button and selecting "Edit", and you can manually create new entries by hitting that big friendly "Add" button:
|
||||
|
||||
|
||||
|
||||
By searching the site directly, you might find that it supports additional search filters which get appended to the URL:
|
||||
|
||||
|
||||
|
||||
You can add those filters to the Query URL to further customize your Custom Search Engine:
|
||||
|
||||
|
||||
|
||||
I spend a lot of my free time helping out on Google's support forums as a part of their [Product Experts program](https://productexperts.withgoogle.com/what-it-is), and I often need to quickly look up a Help Center article or previous forum discussion to assist users. I created a set of Custom Search Engines to make that easier:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
------
|
||||
|
||||
|
|
@ -39,21 +39,21 @@ Even if the site doesn't have a built-in native search, you can leverage Google'
|
|||
```
|
||||
http://google.com/search?q=%s&sitesearch=man7.org%2Flinux%2Fman-pages
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
------
|
||||
|
||||
### Speak foreign to me
|
||||
This works for pretty much any site which parses the URL to render certain content. I use this for getting words/phrases instantly translated:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
------
|
||||
|
||||
### Shorter shortcuts
|
||||
Your Query URL doesn't even need to include a query at all! You can use the Custom Search Engines as a sort of hyper-fast shortcut to pages you visit frequently. If I create a new entry with the Keyword `searchax` and `abusing-chromes-custom-search-engines-for-fun-and-profit` as the query URL, I can quickly open to this page by typing `searchax[tab][enter]`:
|
||||
|
||||
|
||||
|
||||
I use that trick pretty regularly for getting back to vCenter appliance management interfaces without having to type out the full FQDN and port number and all that.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ You can do some other creative stuff too, like speedily accessing a temporary sc
|
|||
data:text/html;charset=utf-8, <title>Scratchpad</title><style>body {padding: 5%; font-size: 1.5em; font-family: Arial; }"></style><link rel="shortcut icon" href="https://ssl.gstatic.com/docs/documents/images/kix-favicon6.ico"/><body OnLoad='document.body.focus();' contenteditable spellcheck="true" >
|
||||
```
|
||||
And give it a nice short keyword - like the single letter 's':
|
||||
|
||||
|
||||
|
||||
------
|
||||
|
||||
|
Before Width: | Height: | Size: 334 KiB After Width: | Height: | Size: 334 KiB |
|
Before Width: | Height: | Size: 136 KiB After Width: | Height: | Size: 136 KiB |
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
date: "2020-09-22T08:34:30Z"
|
||||
thumbnail: images/posts-2020/8p-PSHx1R.png
|
||||
usePageBundles: false
|
||||
thumbnail: 8p-PSHx1R.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- docker
|
||||
- windows
|
||||
|
|
@ -71,12 +71,12 @@ Run the installer, and make sure to tick the box for installing the WSL2 engine.
|
|||
|
||||
#### Step Three: Configure Docker Desktop
|
||||
Launch Docker Desktop from the Start menu, and you should be presented with this friendly prompt:
|
||||
|
||||
|
||||
|
||||
Hit that big friendly "gimme WSL2" button. Then open the Docker Settings from the system tray, and make sure that **General > Use the WSL 2 based engine** is enabled. Now navigate to **Resources > WSL Integration**, confirm that **Enable integration with my default WSL distro** is enabled as well. Smash the "Apply & Restart" button if you've made any changes.
|
||||
|
||||
### Test it!
|
||||
Fire up a WSL session and confirm that everything is working with `docker run hello-world`:
|
||||
|
||||
|
||||
|
||||
It's beautiful!
|
||||
|
Before Width: | Height: | Size: 55 KiB After Width: | Height: | Size: 55 KiB |
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
series: Tips
|
||||
date: "2020-09-13T08:34:30Z"
|
||||
usePageBundles: false
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- linux
|
||||
- shell
|
||||
|
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 42 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: Scripts
|
||||
date: "2020-09-16T08:34:30Z"
|
||||
thumbnail: images/posts-2020/LJOcy2oqc.png
|
||||
usePageBundles: false
|
||||
thumbnail: LJOcy2oqc.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- vmware
|
||||
- powercli
|
||||
|
|
@ -13,7 +13,7 @@ I manage a large VMware environment spanning several individual vCenters, and I
|
|||
|
||||
I can, and here's how I do it.
|
||||
|
||||
|
||||
|
||||
|
||||
### The Script
|
||||
The following Powershell script will let you define a list of vCenters to be accessed, securely store your credentials for each vCenter, log in to every vCenter with a single command, and also close the connections when they're no longer needed. It's also a great starting point for any other custom functions you'd like to incorporate into your PowerCLI sessions.
|
||||
|
Before Width: | Height: | Size: 95 KiB After Width: | Height: | Size: 95 KiB |
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
date: "2020-10-07T08:34:30Z"
|
||||
thumbnail: images/posts-2020/MnmMuA0HC.png
|
||||
usePageBundles: false
|
||||
thumbnail: MnmMuA0HC.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- windows
|
||||
- linux
|
||||
|
|
@ -22,7 +22,7 @@ The instructions worked well for me so I won't rehash them all here. When it cam
|
|||
All I need to do now is execute `sudo ./wsl-vpnkit` and leave that running in the background when I need to use WSL while connected to the corporate VPN.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Whew! Okay, back to work.
|
||||
|
||||
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 69 KiB |
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 103 KiB After Width: | Height: | Size: 103 KiB |
|
Before Width: | Height: | Size: 55 KiB After Width: | Height: | Size: 55 KiB |
|
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 67 KiB |
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 91 KiB After Width: | Height: | Size: 91 KiB |
|
Before Width: | Height: | Size: 305 KiB After Width: | Height: | Size: 305 KiB |
|
Before Width: | Height: | Size: 743 KiB After Width: | Height: | Size: 743 KiB |
|
Before Width: | Height: | Size: 84 KiB After Width: | Height: | Size: 84 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
|
@ -2,8 +2,8 @@
|
|||
series: Projects
|
||||
date: "2020-10-27T08:34:30Z"
|
||||
lastmod: "2021-05-20"
|
||||
thumbnail: images/posts-2020/XtmaR9Z0J.png
|
||||
usePageBundles: false
|
||||
thumbnail: XtmaR9Z0J.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- chromeos
|
||||
- linux
|
||||
|
|
@ -16,7 +16,7 @@ featured: true
|
|||
|
||||
I've [written in the past](/3d-modeling-and-printing-on-chrome-os) about the Linux setup I've been using on my Pixel Slate. My Slate's keyboard stopped working over the weekend, though, and there don't seem to be any replacements (either Google or Brydge) to be found. And then I saw that [Walmart had the 64GB Lenovo Chromebook Duet temporarily marked down](https://twitter.com/johndotbowdre/status/1320733614426988544) to a mere $200 - just slightly more than the Slate's *keyboard* originally cost. So I jumped on that deal, and the little Chromeblet showed up today.
|
||||
|
||||
|
||||
|
||||
|
||||
I'll be putting the Duet through the paces in the coming days to see if/how it can replace my now-tablet-only Slate, but first things first: I need Linux. And this may be a little bit different than the setup on the Slate since the Duet's Mediatek processor uses the aarch64/arm64 architecture instead of amd64. (And while I'm writing these steps specific to the Duet, the same steps should work on basically any arm64 Chromebook.)
|
||||
|
||||
|
|
@ -24,16 +24,16 @@ So journey with me as I get this little guy set up!
|
|||
|
||||
### Installing Linux
|
||||
This part is dead simple. Just head into **Settings > Linux (Beta)** and hit the **Turn on** button:
|
||||
|
||||
|
||||
|
||||
Click **Next**, review the options for username and initial disk size (which can be easily increased later so there's no real need to change it right now), and then select **Install**:
|
||||
|
||||
|
||||
|
||||
It takes just a few minutes to download and initialize the `termina` VM and then create the default `penguin` container:
|
||||
|
||||
|
||||
|
||||
You're ready to roll once the Terminal opens and gives you a prompt:
|
||||
|
||||
|
||||
|
||||
Your first action should be to go ahead and install any patches:
|
||||
```shell
|
||||
|
|
@ -57,7 +57,7 @@ Review it if you'd like (and you should! *Always* review code before running it!
|
|||
sh install.sh
|
||||
```
|
||||
When asked if you'd like to change your default shell to `zsh` now, **say no**. This is because it will prompt for your password, but you probably don't have a password set on your brand-new Linux (Beta) account and that just makes things complicated. We'll clear this up later, but for now just check out that slick new prompt:
|
||||
|
||||
|
||||
|
||||
Oh My Zsh is pretty handy because you can easily enable [additional plugins](https://github.com/ohmyzsh/ohmyzsh/tree/master/plugins) to make your prompt behave exactly the way you want it to. Let's spruce it up even more with the [powerlevel10k theme](https://github.com/romkatv/powerlevel10k)!
|
||||
```shell
|
||||
|
|
@ -72,11 +72,11 @@ We'll need to launch another instance of `zsh` for the theme change to take effe
|
|||
sudo chsh -s /bin/zsh [username]
|
||||
```
|
||||
Now close out the terminal and open it again, and you should be met by the powerlevel10k configurator which will walk you through getting things set up:
|
||||
|
||||
|
||||
|
||||
This theme is crazy-configurable, but fortunately the configurator wizard does a great job of helping you choose the options that work best for you.
|
||||
I pick the Classic prompt style, Unicode character set, Dark prompt color, 24-hour time, Angled separators, Sharp prompt heads, Flat prompt tails, 2-line prompt height, Dotted prompt connection, Right prompt frame, Sparse prompt spacing, Fluent prompt flow, Enabled transient prompt, Verbose instant prompt, and (finally) Yes to apply the changes.
|
||||
|
||||
|
||||
Looking good!
|
||||
|
||||
### Visual Studio Code
|
||||
|
|
@ -86,15 +86,15 @@ curl -L https://aka.ms/linux-arm64-deb > code_arm64.deb
|
|||
sudo apt install ./code_arm64.deb
|
||||
```
|
||||
VS Code should automatically appear in the Chromebook's Launcher, or you can use it to open a file directly with `code [filename]`:
|
||||
|
||||
|
||||
Nice!
|
||||
|
||||
### Android platform tools (adb and fastboot)
|
||||
I sometimes don't want to wait for my Pixel to get updated naturally, so I love using `adb sideload` to manually update my phones. Here's what it takes to set that up. Installing adb is as simple as `sudo apt install adb`. To use it, enable the USB Debugging Developer Option on your phone, and then connect the phone to the Chromebook. You'll get a prompt to connect the phone to Linux:
|
||||
|
||||
|
||||
|
||||
Once you connect the phone to Linux, check the phone to approve the debugging connection. You can then issue `adb devices` to verify the phone is connected:
|
||||
|
||||
|
||||
|
||||
*I've since realized that the platform-tools (adb/fastboot) available in the repos are much older than what are required for flashing a factory image or sideloading an OTA image to a modern Pixel phone. This'll do fine for installing APKs either to your Chromebook or your phone, but I had to pull out my trusty Pixelbook to flash GrapheneOS to my Pixel 4a.*
|
||||
|
||||
|
|
@ -111,11 +111,11 @@ sudo chmod +x /opt/microsoft/powershell/7/pwsh
|
|||
sudo ln -s /opt/microsoft/powershell/7/pwsh /usr/bin/pwsh
|
||||
```
|
||||
You can then just run `pwsh`:
|
||||
|
||||
|
||||
That was the hard part. To install PowerCLI into your new Powershell environment, just run `Install-Module -Name VMware.PowerCLI` at the `PS >` prompt, and accept the warning about installing a module from an untrusted repository.
|
||||
|
||||
I'm planning to use PowerCLI against my homelab without trusted SSL certificates so (note to self) I need to run `Set-PowerCLIConfiguration -InvalidCertificateAction Ignore` before I try to connect.
|
||||
|
||||
|
||||
|
||||
Woot!
|
||||
|
||||
|
|
@ -147,12 +147,12 @@ And finally update the package cache and install `docker` and its friends:
|
|||
sudo apt update
|
||||
sudo apt install docker-ce docker-ce-cli containerd.io
|
||||
```
|
||||
|
||||
|
||||
Xzibit would be proud!
|
||||
|
||||
### 3D printing utilities
|
||||
Just like [last time](/3d-modeling-and-printing-on-chrome-os), I'll want to be sure I can do light 3D part design and slicing on this Chromebook. Once again, I can install FreeCAD with `sudo apt install freecad`, and this time I didn't have to implement any workarounds for graphical issues:
|
||||
|
||||
|
||||
|
||||
Unfortunately, though, I haven't found a slicer application compiled with support for aarch64/arm64. There's a *much* older version of Cura available in the default Debian repos but it crashes upon launch. Neither Cura nor PrusaSlicer (or the Slic3r upstream) offer arm64 releases.
|
||||
|
||||
|
|
@ -174,7 +174,7 @@ conda install -c conda-forge notebook
|
|||
|
||||
You can then launch the notebook with `jupyter notebook` and it will automatically open up in a Chrome OS browser tab:
|
||||
|
||||
|
||||
|
||||
|
||||
Cool! Now I just need to learn what I'm doing with Jupyter - but at least I don't have an excuse about "my laptop won't run it".
|
||||
|
||||
|
Before Width: | Height: | Size: 124 KiB After Width: | Height: | Size: 124 KiB |
|
Before Width: | Height: | Size: 666 KiB After Width: | Height: | Size: 666 KiB |
|
Before Width: | Height: | Size: 60 KiB After Width: | Height: | Size: 60 KiB |
|
Before Width: | Height: | Size: 355 KiB After Width: | Height: | Size: 355 KiB |
|
Before Width: | Height: | Size: 730 KiB After Width: | Height: | Size: 730 KiB |
|
Before Width: | Height: | Size: 229 KiB After Width: | Height: | Size: 229 KiB |
|
Before Width: | Height: | Size: 401 KiB After Width: | Height: | Size: 401 KiB |
|
Before Width: | Height: | Size: 478 KiB After Width: | Height: | Size: 478 KiB |
|
|
@ -2,8 +2,8 @@
|
|||
series: Projects
|
||||
date: "2020-11-24T08:34:30Z"
|
||||
lastmod: "2021-03-12"
|
||||
thumbnail: images/posts-2020/Ki7jo65t3.png
|
||||
usePageBundles: false
|
||||
thumbnail: Ki7jo65t3.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- android
|
||||
- automation
|
||||
|
|
@ -16,7 +16,7 @@ title: Auto-connect to ProtonVPN on untrusted WiFi with Tasker [Update!]
|
|||
|
||||
I recently shared how I use [Tasker and Home Assistant to keep my phone from charging past 80%](/safeguard-your-androids-battery-with-tasker-home-assistant). Today, I'm going to share the setup I use to automatically connect my phone to a VPN on networks I *don't* control.
|
||||
|
||||
|
||||
|
||||
|
||||
### Background
|
||||
Android has an option to [set a VPN as Always-On](https://support.google.com/android/answer/9089766#always-on_VPN) so for maximum security I could just use that. I'm not *overly* concerned (yet?) with my internet traffic being intercepted upstream of my ISP, though, and often need to connect to other devices on my home network without passing through a VPN (or introducing split-tunnel complexity). But I do want to be sure that my traffic is protected whenever I'm connected to a WiFi network controlled by someone else.
|
||||
|
|
@ -45,7 +45,7 @@ You can find instructions for configuring the OpenVPN client to work with Proton
|
|||
- **Country configs** connect to a random VPN node in your target country
|
||||
- **Standard server configs** let you choose the specific VPN node to use
|
||||
- **Free server configs** connect you to one of the VPN nodes available in the free tier
|
||||
|
||||
|
||||
|
||||
Feel free to download more than one if you'd like to have different profiles available within the OpenVPN app.
|
||||
|
||||
|
|
@ -56,7 +56,7 @@ ProtonVPN automatically generates a set of user credentials to use with a third-
|
|||
### Configuring OpenVPN for Android
|
||||
Now what you've got the config file(s) and your client credentials, it's time to actually configure that client.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Launch the OpenVPN for Android app and tap the little 'downvote-in-a-box' "Import" icon.
|
||||
2. Browse to wherever you saved the `.ovpn` config files and select the one you'd like to use.
|
||||
|
|
@ -69,7 +69,7 @@ Success!
|
|||
|
||||
I don't like to have a bunch of persistent notification icons hanging around (and Android already shows a persistent status icon when a VPN connection is active). If you're like me, long-press the OpenVPN notification and tap the gear icon. Then tap on the **Connection statistics** category and activate the **Minimized** slider. The notification will still appear, but it will collapse to the bottom of your notification stack and you won't get bugged by the icon.
|
||||
|
||||
|
||||
|
||||
|
||||
### Tasker profiles
|
||||
Open up Tasker and get ready to automate! We're going to wind up with at least two new Tasker profiles so (depending on how many you already have) you might want to create a new project by long-pressing the Home icon at the bottom-left of the screen and selecting the **Add** option. I chose to group all my VPN-related profiles in a project named (oh-so-creatively) "VPN". Totally your call though.
|
||||
|
|
@ -146,7 +146,7 @@ A1: Variable Clear [ Name:%TRUSTED_WIFI Pattern Matching:Off Local Variables Onl
|
|||
#### OpenVPN Connect app configuration
|
||||
After installing and launching the official [OpenVPN Connect app](https://play.google.com/store/apps/details?id=net.openvpn.openvpn), tap the "+" button at the bottom right to create a new profile. Swipe over to the "File" tab and import the `*.ovpn` file you downloaded from ProtonVPN. Paste in the username, tick the "Save password" box, and paste in the password as well. I also chose to rename the profile to something a little bit more memorable - you'll need this name later. From there, hit the "Add" button and then go ahead and tap on your profile to test the connection.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Tasker profiles
|
||||
Go ahead and create the [Trusted Wifi profile](#trusted-wifi) as described above.
|
||||
|
Before Width: | Height: | Size: 236 KiB After Width: | Height: | Size: 236 KiB |
|
Before Width: | Height: | Size: 138 KiB After Width: | Height: | Size: 138 KiB |
|
Before Width: | Height: | Size: 73 KiB After Width: | Height: | Size: 73 KiB |
|
Before Width: | Height: | Size: 171 KiB After Width: | Height: | Size: 171 KiB |
|
Before Width: | Height: | Size: 157 KiB After Width: | Height: | Size: 157 KiB |
|
Before Width: | Height: | Size: 168 KiB After Width: | Height: | Size: 168 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: Projects
|
||||
date: "2020-11-14T08:34:30Z"
|
||||
thumbnail: images/posts-2020/aeIOr8w6k.png
|
||||
usePageBundles: false
|
||||
thumbnail: aeIOr8w6k.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- android
|
||||
- tasker
|
||||
|
|
@ -13,7 +13,7 @@ title: Safeguard your Android's battery with Tasker + Home Assistant
|
|||
|
||||
A few months ago, I started using the [AccuBattery app](https://play.google.com/store/apps/details?id=com.digibites.accubattery) to keep a closer eye on how I'd been charging my phones. The app has a handy feature that notifies you once the battery level reaches a certain threshold so you can pull the phone off the charger and extend the lithium battery's service life, and it even offers an estimate for what that impact might be. For instance, right now the app indicates that charging my Pixel 5 from 51% to 100% would cause 0.92 wear cycles, while stopping the charge at 80% would impose just 0.17 cycles.
|
||||
|
||||
|
||||
|
||||
|
||||
But that depends on me being near my phone and conscious so I can take action when the notification goes off. That's often a big assumption to make - and, frankly, I'm lazy.
|
||||
|
||||
|
|
@ -29,17 +29,17 @@ I'm not going to go through how to install Home Assistant on the Pi or how to co
|
|||
|
||||
### The Recipe
|
||||
1. Plug the Wemo into a wall outlet, and plug a phone charger into the Wemo. Add the Belkin Wemo integration in Home Assistant, and configure the device and entity. I named mine `switchy`. Make a note of the Entity ID: `switch.switchy`. We'll need that later.
|
||||
|
||||
|
||||
2. Either point your phone's browser to your [Home Assistant instance's local URL](http://homeassistant.local:8123/), or use the [Home Assistant app](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android) to access it. Tap your username at the bottom of the menu and scroll all the way down to the Long-Lived Access Tokens section. Tap to create a new token. It doesn't matter what you name it, but be sure to copy to token data once it is generated since you won't be able to display it again.
|
||||
3. Install the [Home Assistant Plug-In for Tasker](https://play.google.com/store/apps/details?id=com.markadamson.taskerplugin.homeassistant). Open Tasker, create a new Task called 'ChargeOff', and set the action to `Plugin > Home Assistant Plug-in for Tasker > Call Service`. Tap the pencil icon to edit the configuration, and then tap the plus sign to add a new server. Give it whatever name you like, and then enter your Home Assistant's IP address for the Base URL, followed by the port number `8123`. For example, `http://192.168.1.99:8123`. Paste in the Long-Lived Access Token you generated earlier. Go on and hit the Test Server button to make sure you got it right. It'll wind up looking something like this:
|
||||
|
||||
|
||||
For the Service field, you need to tell HA what you want it to do. We want it to turn off a switch so enter `switch.turn_off`. We'll use the Service Data field to tell it which switch, in JSON format:
|
||||
```json
|
||||
{"entity_id": "switch.switchy"}
|
||||
```
|
||||
Tap Test Service to make sure it works - and verify that the switch does indeed turn off.
|
||||
|
||||
|
||||
4. Hard part is over. Now we just need to set up a profile in Tasker to fire our new task. I named mine 'Charge Limiter'. I started with `State > Power > Battery Level` and set it to trigger between 81-100%., and also added `State > Power > Source: Any` so it will only be active while charging. I also only want this to trigger while my phone is charging at home, so I added `State > Net > Wifi Connected` and then specified my home SSID. Link this profile to the Task you created earlier, and never worry about overcharging your phone again.
|
||||
|
||||
|
||||
|
||||
You can use a similar Task to turn the switch back on at a set time - or you could configure that automation directly in Home Assistant. I added an action to turn on the switch to my Google Assistant bedtime routine and that works quite well for my needs.
|
||||
|
Before Width: | Height: | Size: 1.7 MiB After Width: | Height: | Size: 1.7 MiB |
|
Before Width: | Height: | Size: 1.7 MiB After Width: | Height: | Size: 1.7 MiB |
|
Before Width: | Height: | Size: 1.1 MiB After Width: | Height: | Size: 1.1 MiB |
|
Before Width: | Height: | Size: 1 MiB After Width: | Height: | Size: 1 MiB |
|
Before Width: | Height: | Size: 1.4 MiB After Width: | Height: | Size: 1.4 MiB |
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
date: "2020-11-06T08:34:30Z"
|
||||
thumbnail: images/posts-2020/P-x5qEg_9.jpeg
|
||||
usePageBundles: false
|
||||
thumbnail: P-x5qEg_9.jpeg
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- chromeos
|
||||
title: 'Showdown: Lenovo Chromebook Duet vs. Google Pixel Slate'
|
||||
|
|
@ -9,7 +9,7 @@ title: 'Showdown: Lenovo Chromebook Duet vs. Google Pixel Slate'
|
|||
|
||||
Okay, okay, this isn't actually going to be a comparison review between the two wildly-mismatched-but-also-kind-of-similar [Chromeblets](https://www.reddit.com/r/chromeos/comments/bp1nwo/branding/), but rather a (hopefully) brief summary of my experience moving from an $800 Pixel Slate + $200 Google keyboard to a Lenovo Chromebook Duet I picked up on sale for just $200.
|
||||
|
||||
|
||||
|
||||
|
||||
### Background
|
||||
Up until last week, I'd been using the Slate as my primary personal computing device for the previous 20 months or so, mainly in laptop mode (as opposed to tablet mode). I do a lot of casual web browsing, and I spend a significant portion of my free time helping other users on Google's product support forums as a part of the [Google Product Experts program](https://productexperts.withgoogle.com/what-it-is). I also work a lot with the [Chrome OS Linux (Beta) environment](/setting-up-linux-on-a-new-lenovo-chromebook-duet-bonus-arm64-complications), but I avoid Android apps as much as I can. And I also used the Slate for a bit of Stadia gaming when I wasn't near a Chromecast.
|
||||
|
|
@ -20,32 +20,32 @@ I was pretty happy with the Slate, but its expensive keyboard stopped working re
|
|||
|
||||
### Size
|
||||
When you put these machines side by side, the first difference that jumps out is the size disparity. The 12.3" Pixel Slate is positively massive next to the 10.1" Lenovo Duet.
|
||||
|
||||
|
||||
|
||||
The Duet is physically smaller so the display itself is of course smaller. I had a brief moment of panic when I first logged in and the setup wizard completely filled the screen. Dialing Chrome OS's display scaling down to 80% strikes a good balance for me between fonts being legible while still displaying enough content to be worthwhile. It can get a bit tight when you've got windows docked side-by-side but I'm getting by okay.
|
||||
|
||||
Of course, the smaller size of the Duet also makes it work better as a tablet in my mind. It's comfortable enough to hold with one hand while you interact with the other, whereas the Slate always felt a little too big for that to me.
|
||||
|
||||
|
||||
|
||||
### Keyboard
|
||||
A far more impactful size difference is the keyboards though. The Duet keyboard gets a bit cramped, particularly over toward the right side (you know, those pesky braces and semicolons that are *never* needed when coding):
|
||||
|
||||
|
||||
|
||||
Getting used to typing on this significantly smaller keyboard has been the biggest adjustment so far. The pad on my pinky finger is wider than the last few keys at the right edge of the keyboard so I've struggled with accurately hitting the correct `[` or `]`, and also with smacking Return (and inevitably sending a malformed chat message) when trying to insert an apostrophe. I feel like I'm slowly getting the hang of it, but like I said, it's been an adjustment.
|
||||
|
||||
### Cover
|
||||
|
||||
|
||||
The Pixel Slate's keyboard + folio cover is a single (floppy) piece. The keyboard connects to contacts on the bottom edge of the Slate, and magnets hold it in place. The rear cover then folds and sticks to the back of the Slate with magnets to prop up the tablet in different angles. The magnet setup means you can smoothly transition it through varying levels of tilt, which is pretty nice. But being a single piece means the keyboard might get in the way if you're trying to use it as just a propped-up tablet. And the extra folding in the back takes up a bit of space so the Slate may not work well as a laptop on your actual lap.
|
||||
|
||||
|
||||
|
||||
|
||||
The Duet's rear cover has a fabric finish kind of similar to the cases Google offers for their phones, and it provides a great texture for holding the tablet. It sticks to the back of the Duet through the magic of magnets, and the lower half of it folds out to create a really sturdy kickstand. And it's completely separate from the keyboard which is great for when you're using the Duet as a tablet (either handheld or propped up for watching a movie or gaming with Stadia).
|
||||
|
||||
|
||||
|
||||
|
||||
And this little kickstand can go *low*, much lower than the Slate. This makes it perfect for my late-night Stadia sessions while sitting in bed. I definitely prefer this approach compared to what Google did with the Pixel Slate.
|
||||
|
||||
|
||||
|
||||
|
||||
### Performance
|
||||
The Duet does struggle a bit here. It's basically got a [smartphone processor](https://www.notebookcheck.net/Mediatek-Helio-P60T-Processor-Benchmarks-and-Specs.470711.0.html) and half the RAM of the Slate. Switching between windows and tabs sometimes takes an extra moment or two to catch up (particularly if said tab has been silently suspended in the background). Similarly, working with Linux apps is just a bit slower than you'd like it to be. Still, I've spent a bit more than a week now with the Duet as my go-to computer and it's never really been slow enough to bother me.
|
||||
|
Before Width: | Height: | Size: 1.3 MiB After Width: | Height: | Size: 1.3 MiB |
|
Before Width: | Height: | Size: 701 KiB After Width: | Height: | Size: 701 KiB |
|
Before Width: | Height: | Size: 1.1 MiB After Width: | Height: | Size: 1.1 MiB |
|
Before Width: | Height: | Size: 86 KiB After Width: | Height: | Size: 86 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: Tips
|
||||
date: "2020-12-23T08:34:30Z"
|
||||
thumbnail: images/posts-2020/-lp1-DGiM.png
|
||||
usePageBundles: false
|
||||
thumbnail: -lp1-DGiM.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- chromeos
|
||||
title: Burn an ISO to USB with the Chromebook Recovery Utility
|
||||
|
|
@ -17,17 +17,17 @@ Normally that tool is used to creating bootable media to [reinstall Chrome OS on
|
|||
1. Install the [Chromebook Recovery Utility](https://chrome.google.com/webstore/detail/chromebook-recovery-utili/pocpnlppkickgojjlmhdmidojbmbodfm).
|
||||
2. Download the ISO you intend to use.
|
||||
3. Rename the file to append `.bin` on the end, after the `.iso` bit:
|
||||
|
||||
|
||||
4. Plug in the USB drive you're going to sacrifice for this effort - remember that ALL data on the drive will be erased.
|
||||
5. Open the recovery utility, click on the gear icon at the top right, and select the *Use local image* option:
|
||||
|
||||
|
||||
6. Browse to and select the `*.iso.bin` file.
|
||||
7. Choose the USB drive, and click *Continue*.
|
||||
|
||||
|
||||
8. Click *Create now* to start the writing!
|
||||
|
||||
|
||||
9. All done! It probably won't work great for actually recovering your Chromebook but will do wonders for installing ESXi (or whatever) on another computer!
|
||||
|
||||
|
||||
|
||||
You can also use the CRU to make a bootable USB from a `.zip` archive containing a single `.img` file, such as those commonly used to distribute [Raspberry Pi images](https://www.raspberrypi.org/documentation/installation/installing-images/chromeos.md).
|
||||
|
||||
|
Before Width: | Height: | Size: 68 KiB After Width: | Height: | Size: 68 KiB |
|
Before Width: | Height: | Size: 90 KiB After Width: | Height: | Size: 90 KiB |
|
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 72 KiB |
|
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 67 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: Tips
|
||||
date: "2021-01-30T08:34:30Z"
|
||||
thumbnail: images/posts-2020/XTaU9VDy8.png
|
||||
usePageBundles: false
|
||||
thumbnail: XTaU9VDy8.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- vmware
|
||||
title: 'PSA: halt replication before snapshotting linked vCenters'
|
||||
|
|
@ -13,7 +13,7 @@ It's a good idea to take a snapshot of your virtual appliances before applying a
|
|||
|
||||
*(Yes, that's a lesson I learned the hard way - and warnings about that are tragically hard to come by from what I've seen. So I'm sharing my notes so that you can avoid making the same mistake.)*
|
||||
|
||||
|
||||
|
||||
|
||||
Take these steps when you need to snapshot linked vCenters to avoid breaking replication:
|
||||
|
||||
|
Before Width: | Height: | Size: 533 KiB After Width: | Height: | Size: 533 KiB |
|
Before Width: | Height: | Size: 542 KiB After Width: | Height: | Size: 542 KiB |
|
Before Width: | Height: | Size: 917 KiB After Width: | Height: | Size: 917 KiB |
|
Before Width: | Height: | Size: 275 KiB After Width: | Height: | Size: 275 KiB |
|
Before Width: | Height: | Size: 498 KiB After Width: | Height: | Size: 498 KiB |
|
Before Width: | Height: | Size: 185 KiB After Width: | Height: | Size: 185 KiB |
|
Before Width: | Height: | Size: 752 KiB After Width: | Height: | Size: 752 KiB |
|
Before Width: | Height: | Size: 245 KiB After Width: | Height: | Size: 245 KiB |
|
Before Width: | Height: | Size: 766 KiB After Width: | Height: | Size: 766 KiB |
|
Before Width: | Height: | Size: 744 KiB After Width: | Height: | Size: 744 KiB |
|
Before Width: | Height: | Size: 654 KiB After Width: | Height: | Size: 654 KiB |
|
Before Width: | Height: | Size: 71 KiB After Width: | Height: | Size: 71 KiB |
|
Before Width: | Height: | Size: 158 KiB After Width: | Height: | Size: 158 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: vRA8
|
||||
date: "2021-02-22T08:34:30Z"
|
||||
thumbnail: images/posts-2020/7_QI-Ti8g.png
|
||||
usePageBundles: false
|
||||
thumbnail: 7_QI-Ti8g.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- python
|
||||
- rest
|
||||
|
|
@ -100,34 +100,34 @@ Now would also be a good time to go ahead and enable cron jobs so that phpIPAM w
|
|||
Okay, let's now move on to the phpIPAM web-based UI to continue the setup. After logging in at `https://ipam.lab.bowdre.net/`, I clicked on the red **Administration** menu at the right side and selected **phpIPAM Settings**. Under the **Site Settings** section, I enabled the *Prettify links* option, and under the **Feature Settings** section I toggled on the *API* component. I then hit *Save* at the bottom of the page to apply the changes.
|
||||
|
||||
Next, I went to the **Users** item on the left-hand menu to create a new user account which will be used by vRA. I named it `vra`, set a password for the account, and made it a member of the `Operators` group, but didn't grant any special module access.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The last step in configuring API access is to create an API key. This is done by clicking the **API** item on that left side menu and then selecting *Create API key*. I gave it the app ID `vra`, granted Read/Write permissions, and set the *App Security* option to "SSL with User token".
|
||||
|
||||
|
||||
|
||||
Once we get things going, our API calls will authenticate with the username and password to get a token and bind that to the app ID.
|
||||
|
||||
### Step 2: Configuring phpIPAM subnets
|
||||
Our fancy new IPAM solution is ready to go - except for the whole bit about managing IPs. We need to tell it about the network segments we'd like it to manage. phpIPAM uses "Sections" to group subnets together, so we start by creating a new Section at **Administration > IP related management > Sections**. I named my new section `Lab`, and pretty much left all the default options. Be sure that the `Operators` group has read/write access to this section and the subnets we're going to create inside it!
|
||||
|
||||
|
||||
|
||||
We should also go ahead and create a Nameserver set so that phpIPAM will be able to tell its clients (vRA) what server(s) to use for DNS. Do this at **Administration > IP related management > Nameservers**. I created a new entry called `Lab` and pointed it at my internal DNS server, `192.168.1.5`.
|
||||
|
||||
|
||||
|
||||
Okay, we're finally ready to start entering our subnets at **Administration > IP related management > Subnets**. For each one, I entered the Subnet in CIDR format, gave it a useful description, and associated it with my `Lab` section. I expanded the *VLAN* dropdown and used the *Add new VLAN* option to enter the corresponding VLAN information, and also selected the Nameserver I had just created.
|
||||
|
||||
|
||||
I also enabled the options *Mark as pool*, *Check hosts status*, *Discover new hosts*, and *Resolve DNS names*.
|
||||
|
||||
|
||||
|
||||
I then used the *Scan subnets for new hosts* button to run a discovery scan against the new subnet.
|
||||
|
||||
|
||||
|
||||
The scan only found a single host, `172.16.20.1`, which is the subnet's gateway address hosted by the Vyos router. I used the pencil icon to edit the IP and mark it as the gateway:
|
||||
|
||||
|
||||
|
||||
phpIPAM now knows the network address, mask, gateway, VLAN, and DNS configuration for this subnet - all things that will be useful for clients seeking an address. I then repeated these steps for the remaining subnets.
|
||||
|
||||
|
||||
|
||||
Now for the *real* fun!
|
||||
|
||||
|
|
@ -351,10 +351,10 @@ try:
|
|||
You can view the full code [here](https://github.com/jbowdre/phpIPAM-for-vRA8/blob/main/src/main/python/validate_endpoint/source.py).
|
||||
|
||||
After completing each operation, run `mvn package -PcollectDependencies -Duser.id=${UID}` to build again, and then import the package to vRA again. This time, you'll see the new "API App ID" field on the form:
|
||||
|
||||
|
||||
|
||||
Confirm that everything worked correctly by hopping over to the **Extensibility** tab, selecting **Action Runs** on the left, and changing the **User Runs** filter to say *Integration Runs*.
|
||||
|
||||
|
||||
Select the newest `phpIPAM_ValidateEndpoint` action and make sure it has a happy green *Completed* status. You can also review the Inputs to make sure they look like what you expected:
|
||||
```json
|
||||
{
|
||||
|
|
@ -503,7 +503,7 @@ vRA runs the `phpIPAM_GetIPRanges` action about every ten minutes so keep checki
|
|||
Note that it *did not* pick up my "Home Network" range since it wasn't set to be a pool.
|
||||
|
||||
We can also navigate to **Infrastructure > Networks > IP Ranges** to view them in all their glory:
|
||||
|
||||
|
||||
|
||||
You can then follow [these instructions](https://docs.vmware.com/en/vRealize-Automation/8.3/Using-and-Managing-Cloud-Assembly/GUID-410899CA-1B02-4507-96AD-DFE622D2DD47.html) to associate the external IP ranges with networks available for vRA deployments.
|
||||
|
||||
|
|
@ -637,7 +637,7 @@ The full `allocate_ip` code is [here](https://github.com/jbowdre/phpIPAM-for-vRA
|
|||
[2021-02-22 01:31:41,790] [INFO] - Successfully reserved ['172.16.40.2'] for BOW-VLTST-XXX41.
|
||||
```
|
||||
You can also check for a reserved address in phpIPAM:
|
||||
|
||||
|
||||
|
||||
Almost done!
|
||||
|
||||
|
Before Width: | Height: | Size: 378 KiB After Width: | Height: | Size: 378 KiB |
|
Before Width: | Height: | Size: 132 KiB After Width: | Height: | Size: 132 KiB |
|
Before Width: | Height: | Size: 759 KiB After Width: | Height: | Size: 759 KiB |
|
Before Width: | Height: | Size: 221 KiB After Width: | Height: | Size: 221 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
series: Tips
|
||||
date: "2021-02-18T08:34:30Z"
|
||||
thumbnail: images/posts-2020/PPZu_UOGO.png
|
||||
usePageBundles: false
|
||||
thumbnail: PPZu_UOGO.png
|
||||
usePageBundles: true
|
||||
tags:
|
||||
- logs
|
||||
- vmware
|
||||
|
|
@ -11,21 +11,21 @@ toc: false
|
|||
---
|
||||
|
||||
I recently ran into a peculiar issue after upgrading my vRealize Automation homelab to the new 8.3 release, and the error message displayed in the UI didn't give me a whole lot of information to work with:
|
||||
|
||||
|
||||
|
||||
I connected to the vRA appliance to try to find the relevant log excerpt, but [doing so isn't all that straightforward](https://www.stevenbright.com/2020/01/vmware-vrealize-automation-8-0-logs/#:~:text=Access%20Logs%20from%20the%20CLI) given the containerized nature of the services.
|
||||
So instead I used the `vracli log-bundle` command to generate a bundle of all relevant logs, and I then transferred the resulting (2.2GB!) `log-bundle.tar` to my workstation for further investigation. I expanded the tar and ran `tree -P '*.log'` to get a quick idea of what I've got to deal with:
|
||||
|
||||
|
||||
Ugh. Even if I knew which logs I wanted to look at (and I don't) it would take ages to dig through all of this. There's got to be a better way.
|
||||
|
||||
And there is! Visual Studio Code lets you open an entire directory tree in the editor:
|
||||
|
||||
|
||||
|
||||
You can then "Find in Files" with `Ctrl`+`Shift`+`F`, and VS Code will *very* quickly search through all the files to find what you're looking for:
|
||||
|
||||
|
||||
|
||||
You can also click the "Open in editor" link at the top of the search results to open the matching snippets in a single view:
|
||||
|
||||
|
||||
|
||||
Adjusting the number at the far top right of that view will dynamically tweak how many context lines are included with each line containing the search term.
|
||||
|
||||
|
Before Width: | Height: | Size: 1.2 MiB After Width: | Height: | Size: 1.2 MiB |
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 56 KiB |
|
Before Width: | Height: | Size: 493 KiB After Width: | Height: | Size: 493 KiB |
|
Before Width: | Height: | Size: 364 KiB After Width: | Height: | Size: 364 KiB |