Publishing your application

After building your WeWeb application, the final step is to publish it so others can access it. Publishing takes the latest version of your project and makes it available outside the editor.

Your environments

A WeWeb project has up to three environments:

• The editor is where you build and test. Only you and your team see it.
• Staging is a published copy for testing, at https://<your-project>-staging.weweb.io. It is available when your plan includes staging.
• Production is the live app your users open, at https://<your-project>-production.weweb.io until you connect your own domain.

Each environment keeps its own data. Adding a test record in the editor does not create it in production.

Publishing to production

Use production when you are ready for users to access the live version of your app.

1. Click Publish in the top right of the editor.
2. Choose Publish your app.
3. Add a short comment describing what changed (optional), then click Publish.
4. Choose what happens to your data (see below), then confirm.
5. Wait for WeWeb to finish publishing your app.

CHECK BEFORE PUBLISHING

Before publishing, test your main pages, forms, workflows, and authentication flow in preview mode. Publishing makes the current version available to users.

Choosing what happens to your data

If your project uses the WeWeb database or storage, WeWeb asks what to do with your data when you publish. Your changes always go live, but your data only moves if you say so. On your first publish, WeWeb copies your editor data to production. After that, you will usually choose Keep production data, so the data your users created stays untouched. If you changed the structure of your tables, WeWeb also shows a Review Migration window so you can check the change before it goes live.

Learn more about publishing and your data →

Publishing to staging

Staging lets you test a published version of your app before sending it to production.

PLAN REQUIRED

Staging is only available when your plan includes the staging feature.

To publish to staging:

1. Click Publish in the top right of the editor.
2. In the Editor environment card, click Publish to staging, then confirm.
3. Test the staging version of your app.
4. When everything looks good, open the Publish panel again and, in the Staging environment card, click Publish to production. This sends the version that is already in staging to production.

Publish to production is disabled when there is nothing in staging yet, or when staging and production already run the same version.

Accessing previous versions

If you need to restore an earlier editor version, use editor backups.

1. Open the top-level Settings tab.
2. Go to Editor Backups.
3. Find the backup you want to restore.
4. Use Rollback Editor to restore that version.

If the editor no longer loads, you can do the same from the dashboard: click the card of your project, then open the Editor Backups tab.

If a publication goes wrong, you can also put an earlier version back in production from Settings → Publications: open the three dots menu on the version you want and click Restore version vX to production. The same history is in the Deployments tab of your project in the dashboard. Restoring a version depends on your hosting plan: if your plan does not include it, the option is greyed out. See the plans →

Learn more about the publication history →

NEXT STEPS

Enjoyed this directed learning experience? Continue your journey with the WeWeb Academy for more structured tutorials and courses.

Go to the WeWeb Academy →