update readme

Author: lizhuoqi

readme.md

@@ -51,6 +51,7 @@ The `jobsdir` in `configs/crawl.yaml` points to the directory where the job conf
 
 Spec of the job configuration file is as follows:
 ```yaml
+enable: true
 fqljobs:
   -name: zhihu/hotlist
     desc: Know the hot list
@@ -66,22 +67,25 @@ fqljobs:
       cron: "* 3 18/1 * * 5 *" # Every Friday 18:00-23:00
 ```
 
-name
+enable:
+: Required, default false. So, you can disable/enable all the jobs in one yaml.
+
+job.name
 : Required, job name, it needs to be unique in a single yaml configuration file
 
-desc
+job.desc
 : Optional, description information, help memorize and understand
 
-script
+job.script
 : Required, the relative path of the ferret query script. The program will search from the directory specified by `configs/crawl.yaml#fqldir`
 
-output
+job.output
 : Optional, the relative path of the files saved in the fql result. These files will be saved in the directory specified by `config/crawl.yaml#output`. If it is missing, the program will task default value to the format of `config/crawl.yaml#fqldir + '_' + script + .json`, such as *bilibili/weekly* above does not specify *output*, then the default name of the output file automatically generated by the program is `configs_fql_bilibili_weekly.json `
 
-enable
+job.enable
 : Optional, default false. So, only jobs with `enable=true` would be loaded.
 
-schedule
+job.schedule
 : Read `cron` first, if missing, try to read `every`. If boths none exists, the default is *7m*. Because this program uses the [*go-co-op/gocron*](https://github.com/go-co-op/gocron) scheduling library, you can use the *cron expression* when filling in `cron` ; When filling in `every`, you can choose to the following units to define the time frequency, s->seconds, m->minutes, h->hours. If the time interval is very long, such as many days or one month, it is recommended to use *cron expression* to control the time more accurately