Deploy from git

Use a Tokay hosted git repository when you want local development and git push to be the deployment path. After the first connection, the repository stays in your normal git workflow and Tokay prepares updates as pushes arrive.

Last updated

AI agent? Start with llms.txt.

Create or choose the repository

For a Tokay hosted repository, open Add code, choose Git, then create a repository or select one you already have in the Workspace.

Add an SSH key or create a git token before the first push. Choose all repositories, one Workspace, or one repository as its fixed scope. See SSH keys and git tokens for choosing between them.

Push the code

Run the setup commands from the directory containing your local Git repository. If your files are not in Git yet, run git init, add them, and make a commit first.

git remote add tokay <your-repo-url>
git push tokay HEAD

Tokay analyzes the pushed source and lists the Services it can deploy. One repository can contain several Services, such as a web app and a scheduled job.

Review the detected configuration, choose the Service you want, and deploy it. If Tokay does not find a runnable Service, add or clarify an entry point in the repository and push another commit. Tokay analyzes the new push automatically.

Later pushes update the same Services

Each push starts analysis and prepares the affected Services. The Project setting decides whether an update deploys automatically or waits for Update.

The repository page shows detected Services, existing deployments, and candidates that have not been deployed yet. Use that page to add a second Service from the same repository.

Edit locally or in Tokay

The remote leaves your existing upstream unchanged. git push tokay HEAD pushes your checked-out branch under its own name. The first branch pushed becomes the repository default; each Service selects the branch it follows. Change that selection in Service Settings between builds and deployments without stopping the running app.

The Source Code tab can also commit browser edits to the selected branch. Concurrent edits return a conflict and keep your draft. Pull browser commits into your local checkout before pushing again.

Every push goes through review before deployment. New requirements, hardcoded credentials, and build problems surface before the running version changes.