What is the best practice approach with regards to managing the Umbraco Forms data configuration files, e.g. the forms and workflows files?
We weren't sure whether to remove the App_Plugins Forms data from source control completely, or whether to keep it there but exclude those files form our MSBUILD scripts so that we don't keep reverting the forms back on stage or live with our development versions.
I couldn't find any documentation about when exactly Forms reads from the filesystem to update the forms in the DB, or how to stop this process or make it writeonly.
Forms keep form settings and workflows only as files on disk in /app_plugins/forms/data if I remember correctly. So if you change the file, the form changes.
To avoid that your build process overwrites your live forms, you can ignore the files in /app_plugins/forms/data which is the folder containing your forms, workflows etc.
@nikita - to deploy a form, simply deploy the files in /app_plugins/forms/data/ this will deploy your form configuration - its all file based.
What we decided to do was keep the forms data and workflows in our repository for now but exclude them from our MSBUILD scripts so that we don't deploy them to the live server.
It's another thing to worry about now when deploying or pushing from stage to live, but has its benefits.
What's the purpose of the Forms tables in the database now?
Aware of those tables (the Records tables) as I had to manually migrate them from Contour but if I remember correctly there are a bunch of other tables too.
Umbraco Forms and source control, deployment
Hi all,
What is the best practice approach with regards to managing the Umbraco Forms data configuration files, e.g. the forms and workflows files?
We weren't sure whether to remove the App_Plugins Forms data from source control completely, or whether to keep it there but exclude those files form our MSBUILD scripts so that we don't keep reverting the forms back on stage or live with our development versions.
I couldn't find any documentation about when exactly Forms reads from the filesystem to update the forms in the DB, or how to stop this process or make it writeonly.
We would like to know the best practice to deploy forms from one site to other.
For e.g : Copying forms from development to staging site.
Could you please suggest in this regard?
Forms keep form settings and workflows only as files on disk in /app_plugins/forms/data if I remember correctly. So if you change the file, the form changes.
To avoid that your build process overwrites your live forms, you can ignore the files in /app_plugins/forms/data which is the folder containing your forms, workflows etc.
@nikita - to deploy a form, simply deploy the files in /app_plugins/forms/data/ this will deploy your form configuration - its all file based.
@Per - Thank you so much for the info. That was really helpul. :)
What we decided to do was keep the forms data and workflows in our repository for now but exclude them from our MSBUILD scripts so that we don't deploy them to the live server.
It's another thing to worry about now when deploying or pushing from stage to live, but has its benefits.
What's the purpose of the Forms tables in the database now?
@Zac, the database tables collect form submission data from users.
Aware of those tables (the Records tables) as I had to manually migrate them from Contour but if I remember correctly there are a bunch of other tables too.
is working on a reply...