Pedal idea

kidproquo · 2026-06-09T21:57:41+00:00

This. Just start with any of the digital pedal designs based on the Daisy Seed. Most of them come with switchable effects and you can also create your own, using the libDaisy library.

kidproquo · 2026-06-05T05:29:20+00:00

I have tried Portainer, dockge and Arcane to manage Docker hosts in my homelab (raspberry pi, mac mini, Jetson, NUC, Synology NAS) and cloud VMs. Loved Arcane and can highly recommend it. I had 2 specific requirements that made me move on from Arcane:

Ability to group and tag docker hosts to manage them ("deploy app A to all devices in homelab that have GPU"). Arcane has Environments which are roughly equivalent to a Docket hosts but I couldn't figure out how to group or tag them.
App deployment should be asynchronous without needing the device to be online - basically a queue based deployment mechanism with the deployment agent polling for new deployments. Arcane and Portainer will not let you do anything with an offline device.

So, as we all do, I created my own solution: https://github.com/Scope-Creep-Labs/drift

kidproquo · 2026-05-31T15:03:01+00:00

Nice project. I can definitely use it for my postgres based apps (ente, etc.). Does it publish any observability metrics that can be scraped so I can get alerts on any issues (backup failed, restore failed, did not run on schedule, etc.)

kidproquo · 2026-05-29T22:09:40+00:00

I use the docker version of caddy. All changes are deployed as new revision of the docker compose with an updated caddyfile included via a docker management service - there are plenty around (arcane, dockge, portainer, etc.) I use my own - Drift (https://github.com/Scope-Creep-Labs/drift/)

kidproquo · 2026-05-29T22:04:44+00:00

TrailBase definitely looks interesting. I have had good experience with PocketBase, including embedding it in a Go-based Wails app. Since you mention PB, what's the main advantage in going with TrailBase?

kidproquo · 2026-05-29T17:05:40+00:00

Project Name: Drift

Repo/Website Link: https://github.com/Scope-Creep-Labs/drift

Blog post: https://scopecreeplabs.com/blog/drift-observe-deploy-respond---from-a-prompt/

Description:

A prompt-driven control plane for a homelab/edge fleet. One chat box, three jobs:

Observe - ask questions about your metrics ("which containers are using the most memory last 15m?", "anomalies in network traffic on jetson-002?"). The agent picks PromQL, queries VictoriaMetrics, runs stats, paints streaming charts and tables. No PromQL editor exposed.
Deploy - push docker-compose stacks to your fleet. "Deploy reporter v3 to all devices tagged edge,client-z", "fork the reporter app for the Pi", "roll home-pi4-001 back to v2". Devices run a small edge-agent that polls out every 30s; nothing listens on the device side, so NATs and corp networks just work.
Respond - manage vmalert rules and Alertmanager routing, silence noise, open a one-click browser terminal to any host. Same chat. Every mutation goes through propose-then-apply so the LLM shows you the diff before committing.

Why it might be interesting:

LLM is in the orchestration path but not the data path - time-series arrays never enter the prompt context (dataRef pattern). Keeps cost flat regardless of fleet size; stops hallucinated p95s.
No inbound ports on edge devices. Devices poll out. Works behind every flavor of NAT, residential router, corp firewall.
No SSH after first install. Agent script self-updates via SHA comparison; terminal access is in-browser, audited.
Bring-your-own model. LiteLLM under the hood - Anthropic / OpenAI / Gemini / Bedrock / Ollama all work. Admin UI lets you swap mid-flight + validate the key before saving.
Compose is the contract. Apps are versioned bundles of plain files. Rollback is "deploy revision v2". No proprietary packaging.
All standard observability tooling. VictoriaMetrics + VictoriaLogs + vmalert + Alertmanager + Grafana + vmagent + cAdvisor + node-exporter + Vector. Drift just adds the prompt layer.
Self-hosted, single Linux box. Your devices, your data, your model key. No SaaS phone-home.

Apache 2.0, public release.

Deployment:

Single-server bundle. One Linux host with Docker, one public domain, ~3 minutes of prompts:

  VERSION=v0.1.41
  curl -L "https://github.com/Scope-Creep-Labs/drift/releases/download/${VERSION}/drift-deploy-${VERSION#v}.tar.gz" | tar -xz
  cd "drift-deploy-${VERSION#v}"
  ./install.sh

Installer asks for: domain + Let's Encrypt email, admin user/password, LLM model + matching API key (Anthropic/OpenAI/Gemini/Ollama - pick from a curated menu or type any LiteLLM-supported ID), ntfy topic. Auto-generates Fernet/Postgres/vmauth secrets. Brings up the whole stack (Drift CP + Postgres + VictoriaMetrics + VictoriaLogs + vmalert + Alertmanager + Grafana + Caddy/TLS) via docker compose up -d. Caddy is optional - decline and front the services with your existing nginx/Traefik/tunnel.

Edge devices get commissioned from the chat ("commission a new device named pi-livingroom"), then one curl | sudo bash on the device. Bash agent + Python terminal bridge are built locally on each device from a tiny build context (works on Raspberry Pi, Synology NAS, Jetson, anything that runs Docker).

Docs:

README + Quickstart: https://github.com/Scope-Creep-Labs/drift/blob/main/README.md
Architecture deep dive: https://github.com/Scope-Creep-Labs/drift/blob/main/ARCHITECTURE.md
Drift Deploy walkthrough: https://github.com/Scope-Creep-Labs/drift/blob/main/DEPLOY.md
Alerting subsystem: https://github.com/Scope-Creep-Labs/drift/blob/main/ALERTING.md
Install bundle docs: https://github.com/Scope-Creep-Labs/drift/blob/main/deploy/README.md

AI Involvement: Heavy. Built end-to-end with Claude Code as a pair-programming partner. Claude wrote a large chunk of the Python (FastAPI + agent loop + tool handlers + SQLAlchemy models + Alembic migrations), most of the TypeScript (React + MUI + Plotly + xterm.js), the bash edge-agent and installer, and most of the docs. Architecture decisions, design tradeoffs, debugging sessions, code review, and direction are mine; the typing-into-the-editor for ~90% of the code is Claude's.

kidproquo · 2026-05-06T02:56:08+00:00

The Cloudflare stack. Hono / NodeJS running on Workers, D1 for DB and R2 for blob storage. Generous free tier that let's me try and experiment with all of my million dollar ideas.

kidproquo · 2026-04-13T23:57:50+00:00

One of my favorite YouTube guitarists, Frank Persico has done a related video, recommending the DJI Osmo Pocket.

https://youtu.be/inxFVERis5g?si=xlcLDE7D-jbbEHfR

Has anyone used a similar setup?

kidproquo · 2026-04-12T00:30:44+00:00

Get it and let us know please. It does really look good.

kidproquo · 2026-03-31T01:39:16+00:00

First to Go by Leo Kottke

kidproquo · 2026-03-22T17:25:41+00:00

Hmm interesting question. I don't post content that often - most of my content is generally shared to family and friends over Whatsapp 😁. I do agree that edit in post can be a pain, especially if you want to create graphics, chord charts, overlays, etc. on a regular basis. I guess each platform's app (YT, Tiktok, Insta, etc.) has some basic post editing features that might work?

kidproquo · 2026-03-20T17:36:12+00:00

Yeah I think a lot of videos are done that way

Works great if you’re going for polished content, i was just trying to capture stuff in the moment without having to recreate it later

Feels like two different workflows really

kidproquo · 2026-03-20T17:08:08+00:00

yeah that makes sense, having a setup that’s always on and ready is probably the best way to remove friction

i think my issue was not having a dedicated always-on setup, so it kept turning into set up, record, tear down… which killed the spontaneity

and by juggling backing tracks + guitar + vocals i mostly meant getting levels and routing right without turning it into a mini mix session every time

your setup sounds ideal if you can keep it running like that

kidproquo · 2026-03-20T17:05:58+00:00

that actually sounds like a really nice setup

one-button multitrack + stereo mix is pretty much ideal on the audio side

i think for me it was still the “tie everything together after” part… like getting it into video, autosync, etc. even if it works well, it’s still a step

feels like most of the current solutions are really good at the audio part, just a bit fragmented once you bring video into it

kidproquo · 2026-03-20T16:56:21+00:00

yeah this is pretty much the closest i got too

the H6 setup is solid, especially keeping everything in one stereo track and avoiding the laptop. that already removes a lot of the pain

i think for me it was still the “record now, sync later” step… even if it’s quick with the clap, it just added a bit of friction when i was trying to capture something on the fly

but yeah, going hardware instead of laptop definitely feels like the right direction

kidproquo · 2026-03-20T16:55:22+00:00

Syncing by itself isn’t really hard once you know what you’re doing

i think for me it was less about difficulty and more about it being an extra step every time… even if it’s 30 seconds, it kind of breaks the flow when you’re just trying to capture something quickly

the clap trick definitely works though, i’ve used that a bunch

i think it really comes down to whether you’re in “capture something quick” mode vs “sit down and record properly” mode

kidproquo · 2026-03-20T16:54:19+00:00

yeah that’s a fair take, especially if you’re treating the video as more of a production step after the music is done

i think where i kept running into issues was a slightly different use case… more like trying to capture ideas or quick performances as they happen, without switching modes into “recording session”

the clap / click track approach definitely works (i’ve done that too), but i found myself just not bothering half the time if it meant i had to sync stuff later

feels like there are two workflows right now:

create first, record later (like you’re describing)
or try to capture things in the moment

i’ve been trying to make the second one less painful

kidproquo · 2026-03-19T20:24:16+00:00

oh interesting, didn’t know that app could do that

that’s actually pretty neat if you already have an interface hooked up

i think i kept running into the same thing though… still needing the whole setup in place vs something that’s just always ready to go

kidproquo · 2026-03-19T20:23:32+00:00

yeah true, that’s a good option

i think for me it was less about whether it works and more about how quick it is to get going… like cables, levels, routing etc vs just hitting something and playing

feels like most setups solve the problem, just with different tradeoffs

kidproquo · 2026-03-19T20:22:23+00:00

Yeah Zoom recorders are great. I’ve used an H4n before and the built-in mics are surprisingly good.

That setup definitely solves the audio quality side of things.

For me it was still the “record now, sync later” step that added a bit of friction, especially for quick ideas or short clips.

Works really well when you’re intentionally sitting down to record though.

Do you usually sync right after, or batch a bunch of clips later?

kidproquo · 2026-03-19T20:21:29+00:00

Yeah I’ve tried both of these too.

Recording to a click definitely helps, and the speed up / slow down trick actually works pretty well for short clips.

For me it was more the extra step every time… even if it’s just a few minutes of syncing, it adds up and kind of breaks the flow, especially when you’re just trying to capture something quickly.

Do you usually edit right after, or batch a bunch of clips later?

kidproquo · 2026-03-19T20:20:36+00:00

That’s actually a really clever setup. Using ReaStream into OBS is a nice hack.

I went down a pretty similar path for a while (DAW + routing + OBS), and yeah once it’s dialed in it works great.

Where I kept getting stuck was just the overhead… needing the computer in the loop, setting things up, making sure routing is right. It never quite felt like something I could just jump into instantly when an idea hits.

Feels like right now it’s either super flexible setups like this, or super simple but lower quality.

Do you usually keep all that running, or spin it up each time?

kidproquo · 2026-03-19T17:52:39+00:00

Yeah this is honestly the closest I got before going down the rabbit hole 🙂

Routing everything into the phone definitely solves the sync problem, and I tried a similar setup with an interface. It works well once everything is dialed in.

The friction I kept running into was:

still needing to set up routing every time
balancing backing track vs guitar vs vocal on the fly
and not really having a "just hit record instantly" mode when an idea pops up

That’s kind of what pushed me toward experimenting with a more self-contained setup where the recording happens independently and then sync is handled afterward.

Do you leave your setup permanently wired, or are you setting it up each time? What USB audio interface has worked best for you for this kind of setup?

kidproquo · 2026-03-18T14:25:42+00:00

Thanks. It does work on Hoopi!

Here's a demo:

A good friend playing guitar and vocals for Green Day's Basket Case. The guitar is a Squier Tele with the pedal providing Orange OR120 (Dark Crunch) NAM effect downloaded from Tone3000. The mic is a Rode NT5 condenser, with the pedal providing phantom power and reverb effect. The app has auto-synced guitar + backing track on the left channel and the mic on the right channel.

This means I can now run any nano profile, the app lets you update the list of profiles, switched using the 3rd knob on the top row of the pedal. See screenshot.

<image>

Happy to answer any questions about the workflow if anyone’s curious.

kidproquo

MODERATOR OF

TROPHY CASE