Your first deploy

This guide takes code from your clipboard or filesystem to a running Service. The paste and upload flow is useful when you do not have a repository yet. Code already managed in git can follow Deploy from git instead.

Last updated

AI agent? Start with llms.txt.

Bring the code into Tokay

For code on your clipboard or filesystem, open Add code and choose Paste or upload. The editor accepts pasted code, a dragged folder, or one or more selected files.

Uploading several files opens an editor with a file sidebar. Check that the expected files arrived and make any changes before analysis.

Analyze the application

Choose Analyze. Tokay identifies what the code is, how it starts, which Service type it fits, and what values or resources it expects.

When a safe deployment needs a small code change, Tokay shows the proposed diff and explains the reason. A common example is moving a hardcoded API key into an environment variable. Choose Apply changes, return to editing, or continue with the original code.

Review the detected setup

The configuration page shows the Service name, type, and stack detected in the code, along with the branch and the Project the Service goes into. In a new workspace that is a new Project called Default Project, which you can rename before going live. For a scheduled job, set the schedule in plain language and confirm the displayed upcoming runs.

If Tokay does not find a runnable Service, add or clarify an entry point such as server.js, app.py, or index.html, then analyze the code again.

Deploy and verify the result

Choose Go Live, or Test & Schedule for a scheduled job. The tracker moves through Code, Review, Build, and Go Live. A first build usually takes a minute or two, while later updates are often faster.

If the code reads values Tokay cannot supply, such as an API key, the Service page shows a Finish setup panel with a field for each one. Values are saved as Secrets that nobody can read back. Choose Keep it readable only for a value that people and agents with source access may see, then choose Save and go live. Config, secrets, and environment variables explains how those values are shared across the Project.

When it finishes, verify the result for the Service type.

  • Open the URL for a web app.
  • Use Run Now and inspect the output for a scheduled job.
  • Copy the URL and send a test request for a webhook.
  • Check the live logs for a background worker.

The Service page is the operational home for later deployments, logs, environment variables, and settings. See Editing your code for updates and Logs and debugging when the first run does not behave as expected.