Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Purpose of towncrier can be confusing (manual statusboard, no auto monitoring) #5

Open
wvanhed opened this issue Jan 6, 2016 · 0 comments

Comments

@wvanhed
Copy link

wvanhed commented Jan 6, 2016

I think the description (in the README.md file) can be improvement a little bit.

  • only after I got it working, I realized that Towncrier is a manual status board. Originally, I incorrectly thought Towncrier performed monitoring and reporting of a number of services (which are being queried using curl as configured in the fixtures.sh file)
  • consequently, I though fixtures.sh was a sort of config script to define the urls for the monitored services. Instead, it is a script meant to be run on the host (running it in the docker itself is rather impractical) to call the REST api of Towncrier to add services etc. Specifying under 'First run' that the fixtures.sh script is to be run from the host, would make this clearer I think.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant