accounting/bench
2
0
Fork 0
mirror of https://github.com/frappe/bench.git synced 2025-01-23 15:08:24 +00:00
Code Issues Releases Activity

Fixes to Readme

Browse Source
This commit is contained in:
Ankit Javalkar 2014-07-16 15:28:13 +05:30 committed by Pratik Vyas
parent 9474a3a0fb
commit 250a54e78b
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -40,7 +40,7 @@ Basic Usage
* Create a new bench * Create a new bench
The init command will create a bench directory with frappe frameowork The init command will create a bench directory with frappe framework
installed. It will be setup for periodic backups and auto updates once installed. It will be setup for periodic backups and auto updates once
a day. a day.
@ -71,7 +71,7 @@ Basic Usage
Updating Updating
======== ========
On initializing a new bench, a cronjob is add to automatically update the bench On initializing a new bench, a cronjob is added to automatically update the bench
at 1000hrs (as per the time on your machine). You can disable this by running at 1000hrs (as per the time on your machine). You can disable this by running
`bench config auto_update off` and run `bench config auto_update on` to switch `bench config auto_update off` and run `bench config auto_update on` to switch
it on again. To change the time of update, you will have to edit the cronjob it on again. To change the time of update, you will have to edit the cronjob
@ -117,19 +117,19 @@ Frappe Processes
* The WSGI server is responsible for responding to the HTTP requests to * The WSGI server is responsible for responding to the HTTP requests to
frappe. In development scenario (`frappe --serve` or `bench start`), the frappe. In development scenario (`frappe --serve` or `bench start`), the
Werkzeug WSGI server is used and in production, gunicorn (automatically Werkzeug WSGI server is used and in production, gunicorn (automatically
configured in supervisor) in used. configured in supervisor) is used.
* Celery Worker Processes * Celery Worker Processes
* The Celery worker proceses execute background jobs in the Frappe system. * The Celery worker processes execute background jobs in the Frappe system.
These processes are automatically started when `bench start` is run and These processes are automatically started when `bench start` is run and
for production are conifgured in supervisor configuration. for production are configured in supervisor configuration.
* Celery Worker Beat Process * Celery Worker Beat Process
* The Celery worker beat process schedules enqueing of scheduled jobs in the * The Celery worker beat process schedules enqeueing of scheduled jobs in the
Frappe system. This process is automatically started when `bench start` is Frappe system. This process is automatically started when `bench start` is
run and for production are conifgured in supervisor configuration. run and for production are configured in supervisor configuration.
Production Deployment Production Deployment
@ -178,6 +178,6 @@ sudo ln -s `pwd`/config/nginx.conf /etc/nginx/conf.d/frappe.conf
Note: When you restart nginx after the configuration change, it might fail if Note: When you restart nginx after the configuration change, it might fail if
you have another configuration with server block as default for port 80 (in most you have another configuration with server block as default for port 80 (in most
cases for the nginx welcome page). You will have disable this config. Most cases for the nginx welcome page). You will have to disable this config. Most
probable places for it to exist are `/etc/nginx/conf.d/default.conf` and probable places for it to exist are `/etc/nginx/conf.d/default.conf` and
`/etc/nginx/conf.d/default`. `/etc/nginx/conf.d/default`.