#!/bin/bash
input=$(cat)
| --- | |
| argument-hint: [path to source image] | |
| description: Generate favicons from a source image | |
| --- | |
| Generate a complete set of favicons from the source image at `$1` and update the project's HTML with the appropriate link tags. | |
| ## Prerequisites | |
| First, verify ImageMagick v7+ is installed by running: |
| # Claude functions for different providers use litellm | |
| open-laude() { | |
| ANTHROPIC_AUTH_TOKEN=sk-1234 \ | |
| ANTHROPIC_BASE_URL=http://localhost:4000 \ | |
| ANTHROPIC_MODEL=openrouter/qwen/qwen3-coder \ | |
| ANTHROPIC_SMALL_FAST_MODEL=openrouter/qwen/qwen3-coder \ | |
| CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 \ | |
| claude "$@" | |
| } |
| KAMAL_REGISTRY_PASSWORD=dckr_pat_xXXxx_x0xXxXx-xX-XXX0xX0x-x | |
| RAILS_MASTER_KEY=00x00xxx000xxx000000xx0x000x0x00 | |
| POSTGRES_PASSWORD=xXxxx0xXXx0 | |
| MEILI_MASTER_KEY=xXxxx0xXXx0 | |
| BLAZER_DATABASE_URL=postgres://service:{POSTGRES_PASSWORD}@service-name-postgres:5432/service_production |
| ### | |
| ### [2023-06-19] UPDATE: Just tried to use my instructions again on a fresh install and it failed in a number of places. | |
| ###. Not sure if I'll update this gist (though I realise it seems to still have some traffic), but here's a list of | |
| ###. things to watch out for: | |
| ### - Check out the `nix-darwin` instructions, as they have changed. | |
| ### - There's a home manager gotcha https://github.com/nix-community/home-manager/issues/4026 | |
| ### | |
| # I found some good resources but they seem to do a bit too much (maybe from a time when there were more bugs). | |
| # So here's a minimal Gist which worked for me as an install on a new M1 Pro. |
zoomAutenticationTool can be used to escalatMy personal macOS setup guide for a new fresh installation
This repository was ported from Gist to GitHub repository due to these reasons:
.vscode folder.I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.
I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.
"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr
From currying to closures there are quite a number of special words used in JavaScript. These will not only help you increase your vocabulary but also better understand JavaScript. Special terms are normally found in documentation and technical articles. But some of them like closures are pretty standard things to know about. Knowing what the word itself means can help you know the concept it's named for better.