Customization/creation of doctypes in production, what is allowed and what is prohibited?

In a production installation of frappe and/or erpnext

  1. Can the administrator add new doctypes?
  2. Can he modify the existing doctypes and forms?

If yes, are these changes reflected in corresponding files, and how to deal with them? For example, if we push new modifications it can conflict with these changes.

How we should make changes, must we do them locally and then push them to production?

Lastly, what is allowed to do in production?

Thank you in advance.

Hi @oussama-he,

Please check the reference and read the 3,4 and 5 point.

The post is about updating the frappe version.
I want to know if it is a good practice or not to create new doctypes and/or update existing ones in production. Should I make all changes in local dev env and then push them to production?

In production mode (non-development), anything you create/add through the Desk will be saved on the database. So, if you add a new doctype, there will be no files created for these doctypes like in development mode, but the doctype will still be created and saved in the database. And there is nothing wrong with this whether you do it in production mode or not.

However, when you do something that is only saved in the database, you need to keep in mind that the changes you made will be specific to that site only. If you want to keep the changes in the application (for all sites), then you would need to make the changes on your local dev env so the files are generated and saved in the application.

So, it really depends on what you want to do. Do you want to make changes specific to a site? Feel free to do it directly on the Desk of the production. If not, then making the changes from the dev env to be pushed to the production is the way to go.

Hope this helps :thought_balloon:

2 Likes