simon04

Here is a 136 line Python version: https://github.com/simon04/dotfiles/blob/master/.local/bin/e...

Italy has been doing this for decades.[citation needed]

Using a Token2 based id_ed25519_sk_rk key, I found very helpful to configure a different `pushurl` in `.git/config`. This allows to pull via HTTPS w/o a hardware touch.

    [remote "origin"]
            url = https://github.com/freeCodeCamp/devdocs.git
            pushurl = [email protected]:freeCodeCamp/devdocs.git

Ruff's rule is derived from Pylint: https://docs.astral.sh/ruff/rules/unspecified-encoding/

A very tiny router is provided by nanostores: https://github.com/nanostores/router

Maybe not so much for an Internet Protocol router?

Video: https://youtu.be/U7pZbCnJxEw?t=6105 (Kernel Recipes 2025 - Day 2)

Very useful. For configparser.ConfigParser I've found https://stackoverflow.com/a/57307141

Nice, it has landed. Now I'm getting:

> warning: Could not set up terminal for $TERM 'xterm-ghostty'. Falling back to hardcoded xterm-256color values

How could this happen? We're storing deploy credentials in GitHub, and configure fully automated deploy pipelines using YAML and Shell. Escaping 101. xD

https://xkcd.com/1638/

tl;dr?

They're self-hosting at https://gitlab.wikimedia.org/explore

> other CI systems also have this problem, but often provide mechanisms to write individual tasks in other languages

GitLab CI allows to run a bunch of commands in any Docker image you specify. The Docker image and/or your scripts may be self-written.

How do you find, for instance, GitHub Actions more advanced?

Have you tried Gitea Actions? https://docs.gitea.com/usage/actions/overview

Unfortunately typing doesn't fix this. The 2nd callback function argument of Array.map is (index:number), and the 2nd argument of Number.parseInt is (radix:number).

It's a very nasty issue to debug.

Or the good (old) Scanner from http://www.steffengerlach.de/freeware/ (a <1MB executable)

Here you go: https://devdocs.io/playwright/

I'd need to look up the individual scrapers for a fair comparison, since I tend to forget/mixup the challenges. Some scrapers have been around for 10 years and only required little updates.

In general the more native HTML elements and the more descriptive CSS classes are used the easier it gets. Disadvantageous is when great parts of a doc page are built using JavaScript, e.g. when the whole nav is generated dynamically as the nav is typically the source for categorization/grouping on devdocs.

Not that I'm aware of. In a way this contradicts the minimalistic and offline approach.

Here's how to add a new scraper: https://github.com/freeCodeCamp/devdocs/blob/main/.github/CO...

Or open an issue and wait for somebody else to implement the scraper.

The enabled docs are stored in local storage. Are you frequently deleting your browser data? The enabled docs may also be exported as well as re-imported as JSON.