Version control - best practice for modules built in Studio


We’re currently looking for the best way to version control SuiteCRM modules built in Studio as we keep running into the same issues each time we export and import customised modules (and custom modules).

Is there a best practice document anywhere?



i don’t think there’s a single tutorial, with everything (let’s write one!).

You can see this

That explains one of the problems - customizations happen in custom folder, but after a rebuild they affect the database in several ways, namely on the fields_meta_data table and _cstm tables.

So any strategy you devise will either

  • have automated ways of re-generating stuff done in Studio, without Studio, so you can re-run them programmatically

  • have ways of completely capturing the changes Studio makes and re-playing them on a different server

And you have to worry that git checkouts work in sync with these database changes. It’s a bit complicated…

1 Like

Thanks for the pointers 0x00c0ffee :wink:

Yes we’ll probably write an internal Confluence document here but I’m always happy to share knowledge.