Comparing version 0.2.4 to 0.2.5
{ | ||
"name": "commun", | ||
"version": "0.2.4", | ||
"version": "0.2.5", | ||
"description": "🎩 Zero-code platform for creating scalable backends for communities and user based apps", | ||
@@ -5,0 +5,0 @@ "repository": { |
@@ -161,1 +161,13 @@ # Commun | ||
The dashboard also works perfectly on mobile devices, so you can manage your app on the go. | ||
### Production readiness | ||
All the configuration used by Commun is stored in json files, which are updated by the dashboard. | ||
The best practice is to run Commun in development, make all the required changes and then commit these changes to your repository. | ||
In order to deploy, just pull the changes in your production server and restart the node process. | ||
The benefits of this practice are: | ||
* It's easier to test changes in development before moving them to production. | ||
* It's easier to collaborate between team members. You can submit pull requests with your changes and follow the approval process that better fits your organization. | ||
* It's easier to setup a continuous integration system. |
7063
173