DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to rebuild and test SPACE changes with a Tilt loop with SPACE

Run tilt up to rebuild affected images and roll workloads as you edit SPACE files.

Who it is forA contributor changing SPACE services or templates who needs to see runtime behavior on a local Kind cluster.

The problemManually rebuilding images and redeploying the local cluster after every edit is slow and error-prone.

The outcomeEdits trigger rebuilds of affected images and rollouts of their workloads, and you check the change with the Kind smoke suites.

What you need first

  • A host that meets the prerequisites in docs/installation.md
  • Docker-compatible local setup for a Kind cluster, as described in docs/installation.md
  • Bash for installation and cluster diagnostics
  • Git and Python 3.11+ and mdBook 0.4.52 only if you build the docs locally

Steps

  1. Complete [local installation](docs/installation.md) so the Kind cluster is running.
  2. Run tilt up from the repository root.
  3. Edit files and let Tilt rebuild affected images and roll their workloads.
  4. Run the [Kind smoke suites](infra/space/kind/README.md#smoke-test) to check runtime behavior.

Prompt for your agent

In the perplexityai/SPACE repo, after local installation, run `tilt up` from the repository root, then run the Kind smoke suites described in infra/space/kind/README.md. Report which suites pass and fail. Verify that Tilt shows the workloads rolled after your edit.

Caveat. The README points to the Kind runbook for topology and template builds, so expect to read that runbook before changing runtime components.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page