[DOCS-2574] Comment on: "monitoring/tutorial/deploy-mms-in-production.txt" Created: 22/Jan/14 Updated: 16/Mar/15 Resolved: 06/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Katherine Daniels | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 4 weeks ago |
| Description |
|
The docs currently say that only @API_KEY@ needs to be replaced in settings.py in order to run the agent. As of 1.6.8 I found that I had to replace @API_KEY@, @SECRET_KEY@, @DEFAULT_REQUIRE_VALID_SERVER_CERTIFICATES@, and @MMS_SERVER@ in settings.py. It would be great if the docs were updated to reflect this. (The Settings > Monitoring Agent page on MMS itself has the same issue.) |
| Comments |
| Comment by Katherine Daniels [ 22/Jan/14 ] |
|
Upon further investigation @SECRET_KEY@ might not be necessary any more, but the other two still are. |