Versioning, Backups and Restores

Hey Tadabasers!

Over the past few weeks, we’ve put a lot of focus on making it easier to build, track changes and undo mistakes. For example, in support, we’ve seen apps with 1800+ pages where a customer accidentally deleted a parent page which caused them real havoc.

We decided to rebuild the entire backup and restore mechanisms we use. All the updates are interconnected with our upcoming rollout of staging/development app environments for your app.

Here are some of the new updates.

Backups and Restores:
You can now manually trigger a backup of your app. If you’re about to do a large update, we recommend triggering a backup manually first.

The previous backup process didn’t allow our support team to do a selective restore. However, we’ve modified this and added this directly in the builder. If you need to do a restore, simply choose which sections you’d like to restore.

Note: “All Data Tables and Records” restores everything you see in the Data Builder section. Including, Users, subscriptions, tables, and records.

We haven’t set limits on backups as of now, but due to costs associated with hosting many backups, we likely will limit them in the near future.

Track Page/Layout Changes

All page and layout changes are now logged and easily visible so you can see what changes were made, and by whom.

Add ‘commit’ messages to any change.
Especially useful when working with multiple Builders, you can add a comment to each change made to know what was changed and why. Comments are optional by default, but you can force them to be required in your app settings.

If you made a mistake, roll it back to the version before your change.

This same functionality applies to the CSS and Javascript tabs:

Next on our agenda in this update will be the ability to selectively restore parts of the Data Builder, followed by the ability to see logs of changes in the Data Builder. As you can imagine, running manual selective restores on the data builder is more complex as there are data/records we have to manage. For example, if a column was deleted, restoring the column is possible but we have to manage how we deal with the data/new record, etc… This part will be more aligned with the staging environment which we’re also very excited about.

The staging environment will allow you to create a version of your app that you can modify without impacting your production app. Once you’re satisfied with your changes, you’ll be able to promote your latest update to production. During the development process, there will be a unique domain to use for seeing the app-side. This is a huge feature and one we promise for this year, it’s already in the works and we hope to ship as soon as possible.

7 Likes

Fantastic work!!! Not seeing it yet in my builder but sure I will shortly!!!

3 Likes

@moe and Tada Team…hands down, you all are amazing! Keep up the awesome work!

~Adam

4 Likes

Wow, awesome.

Thank you Moe for this update.

4 Likes

Is this feature live yet?

Hi @Markj,

It’s not live yet, but hopefully very soon! We’re doing the finishing touches now.

2 Likes

Still not seeing this even with Alpha turned on. Any idea when it will be available
tks Noel

1 Like

Hi @arthurbuy,

We discovered a critical bug that forced us to revert the update on this. I don’t have an exact time line but it should be soon!

2 Likes

good luck with it tks Noel

Any update on this feature?

hi @moe
I don’t see the Backups and Restores menu from any of my apps. Could you please assist?

1 Like

Hi @sahiraz,

This is something that we’re still working on, sorry for any confusion or inconvenience. We must make sure we get this feature 100% right.

Thanks for the response

Is there any way for ME to download a backup of my database?

Any update on the backup and restore feature?

I think its also very important to offer a way to backup and provide a way to download a sql backup of your database for that app, so we can have that data for safe keeping. The fact that this isn’t available is quite surprising, as there is no real easy way to get data out of Tadabase.

1 Like

@centellix, why not simply use CSV exporting? Once you have it in CSV you can import and use it nearly anywhere. Over 99% of our clients aren’t developers and have no use for a SQL file. I think in 4 years this is only the second request we got for this.

We’re still fine-tuning the backups and restores. It’ll be a few months before this is fully ready on the client-side. It will be re-released again when we have the staging/dev environments built out. They’re very interconnected.

Being able to export all data tables for an APP to CSV would be great. Doesn’t have to be SQL. But from what I understand, backing up would involve exporting each data table to CSV and would be cumbersome.

Is there a way to export ALL or select data tables to a single CSV so I can store that locally as a backup?

Solid point! For now you’d need to create a template for each table, but I agree this should make it much easier to back everything up.

Like everyone else I a really keen to have the full functionality originally described.

After months of work we are planning to roll out our Tadabase app as the core system in our business. I am very nervous of this without a backup/restore system.

But I realised that this post describes ‘user’ access to these features. So I wonder, what backup restore capability is there via Tadabase support?

If needed could you roll back a day for me ? Could you do that selectively on certain tables or pages? I know that I am the wrong side of the Atlantic to have instant access to that option (if it exists) but it’s better than nothing.