neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
Open-source platform to deploy, manage, and scale Docker services on your own VPS. One-command install, automatic HTTPS, and a live topology canvas.
Developer toolsRust · SvelteGitHub @triandamaiOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Shipyard is a self-hosted PaaS built on Docker Swarm and Rust. Deploy from Git or any image, roll back in one click, manage domains with auto-TLS, and monitor your entire cluster — from a dashboard that runs on your own server.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A self-hosted PaaS for deploying and managing containerized applications on your own infrastructure using Docker Swarm and Traefik.
Shipyard gives you a Heroku-like deployment experience on infrastructure you control. Connect your Git repositories, define your services, and Shipyard handles building images, routing traffic, and monitoring deployments — all from a visual topology canvas.Read the full README ↗A self-hosted PaaS for deploying and managing containerized applications on your own infrastructure using Docker Swarm and Traefik.
Shipyard gives you a Heroku-like deployment experience on infrastructure you control. Connect your Git repositories, define your services, and Shipyard handles building images, routing traffic, and monitoring deployments — all from a visual topology canvas.
Key features:
┌─────────────┐ ┌──────────────┐ ┌──────────────┐
│ Browser │───▶│ SvelteKit │───▶│ Rust/Axum │
│ │ │ (Frontend) │ │ (Backend) │
│ │◀───│ │◀───│ │
│ MQTT WS │ └──────────────┘ └──────┬───────┘
└─────────────┘ │
│ ┌───────┼───────┐
│ │ │ │
▼ ▼ ▼ ▼
┌──────────┐ ┌─────────┐ ┌───┐ ┌────────┐
│ rmqtt │ │Postgres │ │Git│ │Docker │
│ broker │ │ DB │ │ │ │Swarm │
└──────────┘ └─────────┘ └───┘ └────────┘
│
┌────▼────┐
│ Traefik │
└─────────┘
Backend crates (backend/crates/):
| Crate | Purpose |
|---|---|
api | Axum HTTP server, REST endpoints, deployment scheduler |
engine | Deployment execution, Docker image build/push |
db | SQLx migrations and query helpers |
docker | Docker API client wrapper |
docker_worker | Worker for Docker Swarm task polling |
git | Git clone/pull operations |
traefik | Traefik dynamic config generation |
mqtt_broker | MQTT client for publishing events |
common | Shared types, errors, config |
docker swarm init)curl -fsSL https://raw.githubusercontent.com/triandamai/shipyard/main/scripts/install.sh | bash
The installer will:
docker stack deployThe installer is idempotent — re-running it updates the deployment while preserving existing secrets.
All configuration lives in /opt/shipyard/.env after installation.
| Variable | Description |
|---|---|
DOMAIN | Your base domain (e.g. example.com) |
ACME_EMAIL | Email for Let's Encrypt TLS certificates |
SHIPYARD__AUTH__JWT_SECRET | JWT signing secret |
SHIPYARD__DATABASE__URL | PostgreSQL connection string |
SHIPYARD__MQTT__USERNAME | MQTT broker username (for backend) |
SHIPYARD__MQTT__PASSWORD | MQTT broker password (for backend) |
When adding a domain to a service, Shipyard auto-generates a subdomain:
<name>.<public-ip>.nip.io — resolves via nip.io wildcard DNS, no DNS config needed<name>.traefik.me — resolves to 127.0.0.1 via traefik.meReal-time events are delivered over MQTT WebSocket. The broker (rmqtt) is configured to require authentication:
| Image | Description |
|---|---|
triandamai827/shipyard-backend:latest | Rust API server |
triandamai827/shipyard-frontend:latest | SvelteKit frontend |
cd backend
cp .env.example .env # fill in DATABASE_URL etc.
cargo run -p api
cd frontend
cp .env.example .env
npm install
npm run dev
cd backend
cargo run -p db --bin migrate
Pull requests are welcome. For major changes, please open an issue first to discuss what you'd like to change.
git checkout -b feat/my-feature)MIT — Copyright (c) 2025 Trian