Skip to content

MANUAL RUN: bring a Hetzner box up and down once (from #345) #452

Closed as not planned

Description

@QuinnsCode

Split out of #345. The tests for the Hetzner box target landed there. A live run needs your Hetzner project token and costs a few cents (a cpx12 plus a 10 GB Volume, billed by the hour), so it's yours to run.

Steps (from a throwaway app with targets.box: { provider: "hetzner" } and no native crates)

  • rustybuns login hetzner (or store a Hetzner token in a codeSplitters repo's Deploy panel).
  • rustybuns plan --stage hetzner-test, then rustybuns deploy --stage hetzner-test. Expect an http://<ip>:3000 URL that answers /health.
  • Deploy again: plan shows an update to the same server, not a create (Alchemy state, SSH key included, carries over).
  • rustybuns destroy --stage hetzner-test --yes, then check the Hetzner console shows no server or Volume left.
  • Hosted path: note the run time against the 13-minute budget, and that the token never shows in the log; then delete the stored key.

Known limit: a box with native/ crates that need the Docker cross-build deploys from the desktop, not the hosted container.

🤖 Generated with Claude Code

Activity

  1. added
    manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it
    on Oct 11, 2026
  2. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Tracked in #609, the one hands-on checklist. The steps here still apply; tick them there.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions