I spent some time recently looking for a cross-platform filesystem to store some personal data. After some deliberation, I settled on a single-volume ZFS "pool" and I'm pretty happy with it. Here's why:
For those who prefer to avoid solutions like iCloud Photos and Dropbox for backing up photos, you can sync your iPhone photos with Syncthing. To do this, you'll need two things:
-
Möbius Sync is, to my knowledge, the only actively-maintained Syncthing client for iOS. It's free to sync up to 20 MB, and only $4.99 (one-time) to remove that limit.
-
PhotoSync is a nifty iOS app for syncing photos to a number of different destinations. It's free for low-quality
GitHub associates a unique resource ID (or "database ID" or just "ID") with each
API-accessible resource. For example, each [issue][issue-id],
[repository][repository-id], and [user][user-id] has a global ID. In my limited
experience with it, GitHub's REST API generally does not expose endpoints by
which resources can be queried by ID (though it does have some [undocumented
endpoints][repo-rest]). These resource IDs have been superseded by distinct
[global node IDs][global-ids] (node_id
). GitHub's GraphQL API allows retrieval
of a node by its ID, called a "direct node lookup".
As you can tell, you likely don't have much reason to interact with the older
Fastmail offers an automated Google Contacts [import feature][import], and also supports importing contacts by CSV and vCard. Unfortunately, I've noticed that all of these import features are lossy. Regardless of import method:
- Contact profile pictures stored in Google Contacts are not imported. (Google exports profile photos by including a link to the photo in the CSV.)
- Birthdays without associated years (i.e., just the month and day) are sometimes not imported at all.
- Empty (
''
) phone numbers are sometimes added to contacts. (This issue may have been a result of me trying to fix the two issues above, and not Fastmail
The best way I've found to automatically merge Dependabot PRs is to use
actions/github-script to comment
@dependabot merge
on Dependabot PRs. There are a few reasons why I think this
approach makes sense:
-
Commenting
@dependabot merge
on a Dependabot PR instructs Dependabot to merge the PR after tests (if any) pass, so we don't need to encode that dependency in a workflow file. -
Unlike using an auto-merge action, nothing happens if the workflow runs on a
It turns out that the order of the --exclude
and --include
flags passed to aws s3 sync
and aws s3 cp
matters, so
aws s3 sync 's3://my-bucket' . --include '*' --exclude '*.png'
won't download anything but
aws s3 sync 's3://my-bucket' . --exclude '*' --include '*.png'
If, when doing something like docker-compose up
, you run into an error like this:
ERROR: Named volume "server/db:/usr/share/nginx/html/db:rw" is used in service "web" but no declaration was found in the volumes section.
You're missing a leading ./
, so, for example:
volumes:
- 'server/db:/usr/share/nginx/html/db'
Some people recommend sending follow-up emails after submitting job applications to improve your chances of getting a response. This /r/cscareerquestions thread comes to mind: I raised the response rate to my applications from 14% to 50% just by sending follow-up emails.
Here's a list of techniques I use when writing follow-up emails. YMMV.