You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, if i create a new site, i could see that its creating a underlying data bases and also installing the frappe components and its related databases.
I feel from a initial setup point it looks corrects.
But from a repeatable build perspective i feel, new-site must just create the necessary assets and configurations to the sites folder.
I would recommend the bench migrate command to perform the applying of changes to the end system. Which gives the ability to configure the configurations with different parameters and can check the real status on the connected parameters and do the database related initializations.
The benefits of the same would be, while dockerizing the final app, i could do the site generation, related assets files during a build stage, but ignore any database requirements at the build stage, and while deploying, i can do a migrate as typical we do any other apps.
The text was updated successfully, but these errors were encountered:
As of now, if i create a new site, i could see that its creating a underlying data bases and also installing the frappe components and its related databases.
I feel from a initial setup point it looks corrects.
But from a repeatable build perspective i feel,
new-site
must just create the necessary assets and configurations to the sites folder.I would recommend the
bench migrate
command to perform the applying of changes to the end system. Which gives the ability to configure the configurations with different parameters and can check the real status on the connected parameters and do the database related initializations.The benefits of the same would be, while dockerizing the final app, i could do the site generation, related assets files during a build stage, but ignore any database requirements at the build stage, and while deploying, i can do a migrate as typical we do any other apps.
The text was updated successfully, but these errors were encountered: