✅ Quick Summary

Push44 connects to the Rocket.new container where your project runs, reads all source files, and pushes them to GitHub. This gives you the full source code — frontend, backend, configuration files, and everything else — exactly as Rocket.new generated and built it.

The Problem

Rocket.new generates complex full-stack projects with backend APIs, databases, and frontend code. Without export capability, all that AI-generated code stays locked in Rocket.new's infrastructure — you can't run it locally, collaborate with developers, or host it yourself.

How Push44 Solves It

Push44 connects to the Rocket.new container where your project runs, reads all source files, and pushes them to GitHub. This gives you the full source code — frontend, backend, configuration files, and everything else — exactly as Rocket.new generated and built it.

Step-by-Step Guide

1

Get your Rocket.new API token

Log into Rocket.new and navigate to your account settings or profile. Find the API token or access token section. Generate a new token and copy it — this authenticates Push44 to your Rocket.new account.

2

Find your project's company ID

In Rocket.new, open your project and look at the URL or project settings. You'll find a company ID (a UUID or alphanumeric identifier) that identifies your workspace. Push44 needs this to access the right project.

💡 Pro Tip
The company ID appears in your Rocket.new project URLs.
3

Connect to Push44

Open Push44, select Rocket.new as your platform, and enter your API token and company ID. Push44 will verify the connection and load your projects.

4

Select and fetch your project

Choose the Rocket.new project you want to export. Push44 connects to the project's container, pings the container to ensure it's running, and then fetches the complete file list.

5

Configure GitHub and push

Enter your GitHub repository details and click 'Push to GitHub'. Push44 pushes all project files as a single atomic commit. Your full Rocket.new project is now on GitHub.

Pro Tips

  • Rocket.new containers sometimes need a few seconds to start — if Push44 shows a connection error, wait 30 seconds and retry.
  • For Rocket.new projects with databases, the schema files are included in the export.
  • Use GitHub to track which version of your Rocket.new project is in production.

Common Mistakes to Avoid

⚠️ Watch Out For
  • Not waiting for the container to fully start before fetching files — Push44 will retry automatically, but give it a moment.
  • Assuming only frontend files are exported — Push44 fetches the complete project including backend code.

Ready to Export?

Push44 is free, open source, and takes under 2 minutes to set up.

Start Exporting Now → View on GitHub

Frequently Asked Questions

Does exporting Rocket.new projects include the backend code?
Yes. Push44 fetches all files from the Rocket.new container, including backend API code, database schemas, configuration files, and frontend code.
Can I run my exported Rocket.new project locally?
Yes, if you have the required runtime environment. The exported files are the actual source code — you can run them locally with the appropriate setup (Node.js, etc.).
Does Push44 work with all Rocket.new project types?
Push44 works with Rocket.new web projects and Android app projects. For Android, it exports the source code; the APK build happens separately.