jb510

Backblaze's bztransmit process loads a file called bzfileids.dat into RAM. This file is a list of all files Backblaze has previously uploaded, including a unique identifier for each file. On most systems, this files is under 100MB in size (paraphrased from Backblaze support rep Zack).

Mine had grown to 6GB. This means that anytime bztransmit runs, it will load this 6GB file into RAM while it is backing up. In doing so it was purging massive ammounts of memory causing behavior like Chrome (usign 10GB of memory on it's own) to hang/beachball for 30 seconds and then refresh all it's windows.

There is no way to alter this behavior once it's begun, aside from starting over with some files excluded. The index needs to be rebuilt from scratch without the excessibe file count, that also means you can't restart and "inherit" a previous backup.

In my case the biggest culprits were .git and node_modules, so I excluded those, started a new backup (transfered licnese) and spent a week hunting for fast internet I could

croxton

Create the bucket

1. Open the console https://console.cloud.google.com
2. If you haven't already, setup your Cloud billing account
3. From the drop down at the top of the screen, create new project for your client, e.g. my-client
4. Make a note of the Project number on the project Home screen (Craft refers to this as the Project ID)
5. In the sidebar go to APIs & Services > Credentials, click the + Create credentials button and choose the Service Account type

• Set account name to craft-cms or similar
• Set role to Owner
• Save

6. Click on the newly created service account email to edit it, then click the Keys tab and click Add key > Create new key and select the JSON format

ademers

How I Update Craft CMS 3.5.x and Craft CMS Plugins

⏳ 2 min read.

Update apnea: the temporary cessation of breath when updating Craft and Craft plugins.

This article describes the steps I follow to update Craft 3.5.x and plugins in a stress-free and reliable manner. 🧘

Photo by Harli Marten on Unsplash