Mercurial > public > scc_access / file comparison
comparison: README.rst
README.rst
- changeset 30
- 4669876326d4
- parent 15
- 93b6b945d939
- parent 29
- 3e3e5bda6b77
- child 33
- ce6eefd1f4b1
equal
deleted
inserted
replaced
| 28:2d90204710af | 30:4669876326d4 |
|---|---|
| 30 You can also use the script by cloning this mercurial repository. | 30 You can also use the script by cloning this mercurial repository. |
| 31 | 31 |
| 32 | 32 |
| 33 Settings | 33 Settings |
| 34 -------- | 34 -------- |
| 35 You will need to provide some user-defined settings in a .yaml format. You | 35 You will need to change some user-defined settings in a settings.yaml file. You |
| 36 can rename the settings_sample.yaml file to settings.yaml and follow the instructions | 36 can copy the settings_sample.yaml file to settings.py and follow the instructions |
| 37 there. | 37 there. You can copy the resulting file to your home directory as `.scc_access.yaml`. |
| 38 This is the default location, `scc_access` will search there if no other location was | |
| 39 specified. | |
| 38 | 40 |
| 39 Specifically, you will need to: | 41 Specifically, you will need to: |
| 40 | 42 |
| 41 1. Change the BASIC_LOGIN and DJANGO_LOGIN to your credentials. | 43 1. Change the `basic_credentials` and `website_credentials` to your credentials. |
| 42 2. Change the OUTPUT_DIR to the location were the results will be stored. | 44 2. Change the `output_dir` to the location were the results will be stored. |
| 43 | 45 |
| 44 Please not that it's not a good idea to store your stations management credentials in the settings | 46 Please not that it's not a good idea to store your stations management credentials in the settings |
| 45 file. The standard user has "Station Management" privileges and if the credentials | 47 file. The standard user has "Station Management" privileges and if the credentials |
| 46 are stolen, someone could change/delete the stations settings from the SCC database. | 48 are stolen, someone could change/delete the stations settings from the SCC database. |
| 47 For this, it is better to use a used account with minimum access settings, that | 49 For this, it is better to use a used account with minimum access settings, that |
| 51 Usage | 53 Usage |
| 52 ----- | 54 ----- |
| 53 | 55 |
| 54 You can upload a file specifying the username and the system id:: | 56 You can upload a file specifying the username and the system id:: |
| 55 | 57 |
| 56 scc_access 20110101po01.nc 125 | 58 scc_access upload-file 20110101po01.nc 125 |
| 57 | 59 |
| 58 If you want to wait for the processing to finish and download the resulting files | 60 If you want to wait for the processing to finish and download the resulting files |
| 59 you need to define the -p flag:: | 61 you need to define the `process-file` command. Use the `-p` flag to wait for the |
| 62 result:: | |
| 60 | 63 |
| 61 scc_access 20110101po01.nc 125 -p | 64 scc_access process-file 20110101po01.nc 125 -p |
| 62 | 65 |
| 63 If you want to delete an existing measurement id from the database use the -d flag and | 66 If you want to delete an existing measurement id from the database use the `delete` |
| 64 the measurement id:: | 67 command and the measurement id:: |
| 65 | 68 |
| 66 scc_access -d 20110101po01 | 69 scc_access delete 20110101po01 |
| 70 | |
| 71 You can list available measurements with the `list` command:: | |
| 72 | |
| 73 scc_access list | |
| 67 | 74 |
| 68 For more information on the syntax type:: | 75 For more information on the syntax type:: |
| 69 | 76 |
| 70 scc_access -h | 77 scc_access -h |
