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

Bring the code into Tokay

From the dashboard, choose Deploy your first service or New Service. Paste code, drag in a folder, or choose one or more files from the file picker.

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, stack, and values detected in the code. Supply private environment variable values before deployment. 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 Deploy, 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.

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.