| /** | |
| * @param {import("@11ty/eleventy/src/UserConfig")} eleventyConfig | |
| */ | |
| module.exports = (eleventyConfig) => { | |
| return {}; | |
| }; |
I recently (re)switched from using Netatalk to Samba for file access from macOS (15.x) to linux (AlmaLinux 9.x).
Obviously the Samba is a great resource, on the Samba Wiki the Configure Samba to Work Better with Mac OS X was invaluable for setting up the /etc/samba/smb.conf file, and the vfs fruit man page contains documentation for all the options.
Here is the /etc/samba/smb.conf file I use:
# See smb.conf.example for a more detailed config file or
| # latest supported electron version as of october 2024 | |
| LATEST_SUPPORTED_VERSION=30 | |
| RED='\033[0;31m' | |
| GREEN='\033[0;32m' | |
| NC='\033[0m' # no color | |
| mdfind "kind:app" 2>/dev/null | sort -u | while read app; | |
| do | |
| filename="$app/Contents/Frameworks/Electron Framework.framework/Electron Framework" | |
| if [[ -f $filename ]]; then |
I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.
I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:
By default, cache location when running CI tasks is /opt/hostedtoolcache. It's okay to change it by setting 3 envvars in config.yaml
runner:
envs:
RUNNER_TOOL_CACHE: /path/to/cache
AGENT_TOOLSDIRECTORY: /path/to/cache
RUN_TOOL_CACHE: /path/to/cache
Microsoft claims Visual Studio Code (VS Code) is open source, yet it restricts the use of its Marketplace extensions in non-Microsoft products like VSCodium (telemetry/tracking free open source fork), Cursor, Windsurf, Trae, and other VS Code-based IDEs, enforcing what some see as monopolistic control. This guide provides a workaround to enable the VS Code Marketplace in VSCodium and Trae (more to be added soon), allowing you to freely use extensions. Note that using the VS Code Marketplace with non-Microsoft products may violate its terms of use, which state that extensions are intended for use only with Microsoft Visual Studio products. Proceed at your discretion after reviewing the terms.
To configure VSCodium to use the VS Code Marketplace instead of the default OpenVSX Registry, you can either set environment variables or create a custom product.json file.