devpush

Fair enough. I actually needed dns-01 for /dev/push [1] so ended up not using it. I still thought it was a pretty cool project. [1]: https://github.com/hunvreus/devpush

Some interesting concepts: - Components: https://hyperflask.dev/guides/components/ - Bundling view and controller in the same file: https://hyperflask.dev/guides/interactive-apps/ I think these may be footguns though. Components for example are just a regular macros under the hood. Why not use macros then? I'm also curious about the choice of Flask. I started with a similar approach for /dev/push [1], but ended up moving to FastAPI + Jinja2 + Alpine.js + HTMX once I figured out FastAPI wasn't just for APIs. I wanted proper async support. I love Flask, but don't you find it limiting? [1]: https://github.com/hunvreus/devpush

I'm still trying to figure out what the key difference would be when writing an app with Datastar over HTMX. I wrote /dev/push [1] with FastAPI + HTMX + Alpine.js, and I'm doing a fair bit with SSE (e.g. displaying logs in real time, updating state of deployments across lists, etc). Looking at the Datastar examples, I don't see where things would be easier that this [2]: <div hx-ext="sse" sse-connect="{{ url_for('project_event', team_id=team.id, project_id=project.id) }}" sse-close="sse:stream_closed" > <div hx-trigger="sse:deployment_creation, sse:deployment_status_update, sse:deployment_rollback, sse:deployment_promotion" hx-get="{{ url_for('project_deployments', team_slug=team.slug, project_name=project.name).include_query_params(fragment='deployments') }}" hx-target="#deployments

> 1. Is there a support for deploying into a multiple machines? If so, how does it work? Working on that, you should soon be able to have a central /dev/push instance and remote nodes managed by it. > 2. Where and how secrets are stored? Environment variables are stored in the DB but encrypted using Fernet (https://github.com/hunvreus/devpush/blob/main/app/models.py).

I have a draft ARCHITECTURE.md file in the repo: https://github.com/hunvreus/devpush/blob/main/ARCHITECTURE.m... I'm also working on adding manual steps so that folks who prefer to deploy the app themselves can do so. I initially had the app deployed with Terraform + Ansible, but rewrote it as a bash script as I thought it'd be lower friction.

Thanks for mentioning Basecoat. Funny enough, I've used a very similar stack (HTMX + FastAPI) for /dev/push [1]. Code is available there: https://github.com/hunvreus/devpush Planning on checking out holm soon. [1]: https://devpu.sh

I wanted to deploy Python apps but still wanted to have a polished UX experience, like Vercel has. So I built /dev/push for myself, and then decided to open source it. You can host it on a Debian/Ubuntu box by running a single command: curl -fsSL https://raw.githubusercontent.com/hunvreus/devpush/main/scripts/prod/install.sh | sudo bash It's pretty similar to Vercel or Laravel Cloud: - Git-based deployments, - Environment management, - Real-time monitoring, - Team collaboration, - Custom domains, - ... For now it's mostly Python and Node.js (in beta), but I'm working on adding other languages (PHP, Go, Ruby). Many other things in the works: persistent storage, SQLite databases, scaling/resources settings, custom containers, remote nodes, etc. It's a beta, but it's fully functional: - Website: https://devpu.sh - GitHub: https://github.c