Environment
Set up a Paradev (formerly Superset) cloud environment end to end from this machine -...
Install
npx skills add ParadevAI/Paradev --skill environment -g -a claude-code -y- Repository
- ParadevAI/Paradev15.8k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 2,055 tokens
- Runs scripts
- No, instructions only
What it does
Set up a Paradev (formerly Superset) cloud environment end to end from this machine - work out what the repositories need, set the environment's variables, boot a cloud box on it, get the project running there, and save checkpoints until new cloud workspaces start ready. Use when the user asks to set up, onboard, or finish a cloud environment, or when a setup session hands you an environment ID.
Cloud environment setup
Goal: a cloud environment that new cloud workspaces boot straight into, with dependencies installed, variables set, and services starting on boot. You run on the user's machine with their Paradev login. You build the environment by driving a cloud box from here.
Terms you will use with the user:
- Environment: what a cloud workspace boots from. It has repositories (the first is primary), variables, a region, and a visibility.
- Box: one cloud workspace running on the environment.
- Checkpoint: a snapshot of the box saved into the environment, so the next workspace starts from it.
superset environments replacesaves one. Only the latest checkpoint is kept.
What a box already has
Do not install or upgrade these:
- Node 24, Bun, Python 3 (pip, pipx, venv), a JDK, build-essential, clang, git, git-lfs,
gh, and Docker with Compose. They come with the image, and a checkpoint keeps the versions it was saved with. - Chrome, Claude Code, Codex and the
supersetCLI. Every boot updates them to the platform's current release, so a checkpoint does not freeze their versions. - A Linux desktop (XFCE over VNC, Xvfb), ffmpeg and ImageMagick.
- GitHub access for git and
gh. Do not rungh auth loginor put a token in the box.
There is no macOS: no Xcode, iOS simulator or Safari. If the project needs one, tell the user. Install only what the project needs, and do it through .superset/config.toml so a fresh checkout repeats it.
0. Connect GitHub
Boxes check out repositories through the organization's Paradev GitHub App. Run superset integrations github status. If the App is not installed, run superset integrations github connect and ask the user to finish the install in the browser. It needs the Pro plan and a GitHub account that can install apps on the repositories' owner.
