KO
|
EN
gitlite — search
Search
#typescript
#ai-agents
#deepseek-harness
#dsh-plugin
#open-source
#ai
#cli
#dsh
#claude-code
#codex
#developer-tools
#react
adminyo
★ 18
Open GitHub ↗
Admin panel driven by YAML build in Rust.
Download README (.md)
Explore Similar Repositories
flutter-conference-app
:
A simple whitelabeled app for conferences written in Flutter
marketplace-docker
:
Whitelabel NFT marketplace by Unique Network.
AndroidTemplate
:
AndroidTemplate repository provides modern android app base and useful POCs to build new apps upon it.
XToolkit.WhiteLabel
:
Modular MVVM framework for fast creating powerful cross-platform applications with Xamarin & .NET for Mobile
WhiteLabelled
:
An example of how to achieve white-labelling without duplicating targets.
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
adminyo
?
Download (.md)
<p align="center"> <img src="img/adminyo-img-0.svg" alt="Adminyo" width="128" height="128" /> </p> <h1 align="center">Adminyo</h1> <p align="center"> <a href="https://www.npmjs.com/package/@adminyo/cli"><img src="https://img.shields.io/npm/v/@adminyo/cli?label=npm&logo=npm" alt="npm package" /></a> <a href="https://github.com/felipeinf/adminyo/stargazers"><img src="https://img.shields.io/github/stars/felipeinf/adminyo?style=social" alt="GitHub stars" /></a> </p> <p align="center"><code>rust</code> · <code>admin</code> · <code>dashboard</code> · <code>yml</code> · <code>whitelabel</code></p> Generic admin panel driven by YAML, backed by a Rust binary and a pre-built React UI. Distributed via npm with native optional dependencies. ## Requirements - **End users**: Node.js 18+ (only for the npm wrapper that launches the native binary). No Node at runtime for the panel server. - **Building from source**: Rust stable, Node 18+ for the UI build. ## Install ```bash npm install @adminyo/cli ``` Version `@adminyo/cli` and every `@adminyo/cli-*` package with the same semver. ## User project (after `nyo init`) ``` ./ adminyo.yml envs.yml .env assets/ ``` ## Commands | Command | Description | |--------|-------------| | `npx nyo init` | Scaffold `adminyo.yml`, `nyo.example.yml`, `envs.yml`, `.env.example`, `assets/` | | `npx nyo dev` | Run panel (default `http://127.0.0.1:4321`) with hot-reload and proxy | | `npx nyo dev --env=staging --port=8080` | Other env / port | | `npx nyo validate` | Validate YAML without starting the server | | `npx nyo build [--env=production] [--out=dist]` | Emit static `dist/` (`config.json` + SPA) for S3/Amplify/Vercel | Static hosting: set `auth` in `adminyo.yml` so the SPA logs in against your API and stores the token in `sessionStorage`. The browser calls `baseUrl` directly; your API must allow CORS for the panel origin. Define `columns` per entity in YAML if the API is not reachable at build time (live inference is skipped for `nyo build`). ## REST conventions - **List**: `GET {entity.endpoint}` — JSON array at root or first object key whose value is an array of objects. - **Detail**: `GET {endpoint}/{id}` - **Create**: `POST {endpoint}` with JSON body - **Update**: `PUT {endpoint}/{id}` with JSON body - **Delete**: `DELETE {endpoint}/{id}` ## Pagination (when configured) - **offset**: `?page=1&limit={pageSize}` (1-based page) - **cursor**: `?cursor={token}` (opaque; first page omits `cursor`) ## Auth - **`nyo dev` (default)**: `POST /auth/login` with JSON `{ "user", "pass" }`, JWT in httpOnly cookie `adminyo_token`. - **`nyo dev` with `auth` in `adminyo.yml`**: login goes to your API; same cookie/JWT flow as above is not used for upstream (see schema). - **`nyo build` (static)**: `POST {baseUrl}{auth.loginEndpoint}`; bearer token from `auth.tokenPath` in `sessionStorage`. - `401` from the Nyo server includes `"source":"adminyo"` in JSON body; upstream API errors pass through without that field.
