- Deploy the app using the Heroku button, set
GITHUB_REPO
to the name of the repo you want to use. - Write stuff in Github issues of the
GITHUB_REPO
repo.. - When you're ready to publish an issue as a blog post, you close the issue
and apply the
published
label. - Blog entries are cached for 15 minutes, and the markdown content is cached
based on the SHA digest of the issue's body. If you need to force a refresh
sooner, just force-refresh the page in your browser (i.e. send
Cache-Control: no-cache
). Force-refresh requests are throttled so that you can force-refresh at most every 15 seconds. - Your visitors can comment on the corresponding Github issue.
Note: We force the application of a specific label since anyone can create issues, and you don't want people being able to publish anything on your website.
You should probably register a Github application to increase the API
rate-limit (defaults to 60 req/s for anonymous requests):
https://github.com/settings/applications. Then, set GITHUB_CLIENT_ID
and
GITHUB_CLIENT_SECRET
.
For the list of supported options, please see the app_config.rb
initializer.
from https://github.com/crohr/ebarnouflant
No comments:
Post a Comment