Resource
guide.
Tools, tutorials, and references for software development, study, local AI, networking, and self-hosted services.
Each entry explains what it does, common uses, requirements, and limitations, with links to documentation.
Browse by topic.
Browse these topics or search the full collection.
Web development.
HTML, CSS, layout, accessibility, APIs, and introductory courses.
Web fundamentals → STUDYStudy tools.
Text-to-speech, document questions, audio summaries, and study workflows.
Learning & study → AILocal AI.
Model downloads, inference runtimes, chat interfaces, and hardware requirements.
AI & local models → SELF-HOSTINGMedia servers.
Media requests, library management, playback, containers, and remote access.
Media server →USAGE GUIDES
STUDY TOOLSAll collections.
Browse resources by subject. Entries include descriptions, practical uses, and limitations.
Using the guide.
Resource entries include documentation links and relevant platform, licensing, and maintenance information.
- Browse or search.Select a collection or search by name, topic, or use.
- Read an entry.Open a resource to see its features, common uses, requirements, and sources.
- Save resources.The save button adds an entry to a list stored in this browser. An account is not required.
Example agent configuration.
Hermes can run on a Linux host with a remote model provider, local tools, persistent memory, a Markdown vault, and optional integrations. The hardware below is an example configuration, not a minimum requirement.
Request flow
A CLI or messaging request goes to Hermes, which calls a model and tools and returns a response. Memory and a Markdown vault can retain information between sessions.
Optional integrations
Google Workspace, YouTube, messaging, GitHub, and Vercel support communication, research, and deployment tasks. Connections require separate authorization. Restrict permissions and review actions that send messages or change data.
Media-server workflow.
Seerr
Radarr / Sonarr
Prowlarr supplies indexers
qBittorrent + qui
Gluetun → Proton VPN
Jellyfin
Bazarr adds subtitles
Portainer manages containers, Twingate provides private access, Dozzle displays logs, and Cleanuparr manages cleanup. n8n can connect services through automation workflows. Only obtain and share authorized media.
Domains and DNS
A registrar such as Porkbun handles domain registration and renewal. A DNS provider such as Cloudflare manages records for hostnames such as jellyfin.example.com. A public HTTPS endpoint can allow access without a VPN.
Public and private access
DNS alone does not expose a private server or secure it. Public access requires a reachable endpoint, HTTPS, and authentication. A reverse proxy, tunnel, or port-forwarding rule may provide that network path. Twingate is an alternative for private access; DNS records do not establish a Twingate connection.
Setup steps +
- Configure containers, volumes, permissions, and backups. Start with Jellyfin and authorized media.
- Keep administration private. Verify remote-access policies before relying on them.
- Configure Gluetun and Proton VPN before attaching qBittorrent; verify routing and fail-closed behavior.
- Add library managers, requests, subtitles, and logs. Test cleanup rules before allowing deletion.
Eligibility and renewal terms.
Eligibility, region, enrollment verification, and renewal terms vary by provider. Some offers are ongoing; others are limited, paused, or expired. Check the status and official terms linked in each entry before signing up. Set a reminder before a trial renews.
Video descriptions and compatibility.
Channels and videos covering web development, networking, homelabs, local AI, Apple development, and 3D modeling. Descriptions summarize public channel and video information; they are not full reviews of every video.
Filter by topic, or use youtube-channel and youtube-video to select a format. Check publication dates and software versions before following a tutorial. Product reviews, commentary, and sponsored videos may require additional verification.
Build tools and editor extensions.
Vite combines a development server, module updates, and a production build command. webpack is a configurable module bundler built around a dependency graph. They solve overlapping problems and use different configuration formats.
New frontend projects
Use Vite’s official guide or the framework’s recommended setup. The development server and production build serve different purposes. The Vite entry includes setup steps and guidance on environment variables.
Existing codebases
Review the existing scripts, plugins, and framework requirements before changing the toolchain. webpack, Rollup, esbuild, Parcel, and Rspack differ in configuration, output, and compatibility.
VS Code extension selection +
Start with language support for the project. ESLint checks configured code rules, Prettier formats code, and EditorConfig shares whitespace settings. Error Lens, GitLens, Tailwind CSS IntelliSense, and axe Accessibility Linter support specific tasks. Emmet is built into VS Code for supported file types.
Check the publisher, workspace trust settings, and formatter configuration before installing extensions. VS Code’s extension guide explains that extensions have the same permissions as the editor.
All resources.
Tools, tutorials, and references organized by topic.
No resources found.
Try another query, switch collections, or reset the filters.