You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.
Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.
How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
How to deploy Standalone Ansible Automation Platform (AAP) - container based deployment
🚀 Deploying Ansible Automation Platform (AAP) on a Standalone Linux Machine
This guide demonstrates how to deploy Red Hat's Ansible Automation Platform (AAP) in a standalone, containerized setup. It assumes you already have a Linux machine ready for deployment.
Instance Specifications
I'm using an OpenStack instance with the following specifications:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Windows PowerShell script to auto update the qBittorrent port to latest ProtonVPN port forward
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Enabling VS Code Marketplace in VSCodium
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.