Replace your bot ZIP without a new project or another payment

Update code in an existing Deployka project: ZIP, ENV, entrypoint, persistent data, and verification after deployment.

Update the existing project

Fixing your bot code does not require a new project or another plan purchase. Open the appropriate container project under Projects and use Replace ZIP. Do not delete a paid project just to update its source code.

Prepare the archive

• Include source files and a dependency manifest, such as requirements.txt for Python or package.json with a lockfile for Node.js.
• Point to an existing entrypoint. A Python example is worker: python main.py in Procfile. Adjust the command if your file has a different name.
• Exclude .env, BOT_TOKEN, API keys, node_modules, and your local virtual environment.
• Do not package the live SQLite database with your source code. Check its persistent path and backup separately.

Replace the code

1. Open the current project and verify that it belongs to the bot you intend to update.
2. Check ENV and the entrypoint. Add new required variables in the project editor, not in a public ZIP.
3. Select Replace ZIP, upload your archive, and review source validation results.
4. Follow the deployment task and Logs. If it fails, correct the reported cause in the same project and retry.

Source replacement preserves the plan association, project settings, and persistent /data. Files outside the persistent volume are not guaranteed to survive. An update can interrupt your bot; ZIP replacement does not promise zero downtime.

Verify the result

Do not rely only on the running label. Send a test message, try the changed command, and read a previously stored record. Check logs for repeating tracebacks or continuous restarts.

If the button is unavailable or a task is stuck

Do not create a second paid project. Contact support with the project name, time of the attempt, and the error text without secrets. Check any active deployment task first: concurrent ZIP replacement can be temporarily unavailable.

For Unauthorized, check BOT_TOKEN. For ModuleNotFoundError, add the missing dependency. For polling/webhook conflicts, check your Telegram bot mode and other running instances. Buying Nano does not, by itself, repair these code errors.

Persist SQLite in /data · Prepare a project from ChatGPT · Open Projects · Support