Upgrade path for different versions and development workflow

English Forum Questions
1

I have done some internal testing with NocoBase.

Now I want to evaluate how well it will do if I develop real-world solutions for my clients.

How is the development workflow?

  • How do I get the changes to the clients installation? I mean the diff between two versions, not the initial deployment
  • So when I change the database structure in my development version, how is this migrated for clients?

Hopefully, I don’t need to “re-click” everything?

2

Hi, in the development environment, you can freely modify database structures, fields, relations, views, and workflows.
For detailed guidance, please refer to:
https://docs.nocobase.com/handbook

When you need to synchronize these changes (data structure, views, workflows, etc.) to the production environment, you can use the Migration plugin.
It allows you to export migration files from the development environment and import them into the production environment to apply the changes.
https://docs.nocobase.com/handbook/migration-manager

1 Like
3

Thank you for your explanation, that helps!

In order to use the plugin, the Professional Version (8.000$) is needed, which is a steep curve for evaluating it for use in clients projects.

While I see the value for a professional version, I think especially for cases like me (small company, but still professional dev pipeline in the background, projects sell for less than the pro version) some middle ground would be better fitting and affordable.

4

Did you manage to find away to overcome the problem with free edition? Im trying to achieve same thing