3 Коммитов

Автор	SHA1	Сообщение	Дата
Jeff King	470f1a93f1	swap out API_USER/API_PASS for GITHUB_API_TOKEN ... The use of bare username/password combos to do API calls has been dropped by GitHub, as of 2020-11-13: https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-endpoint/ Let's switch to expecting a token in the rake jobs that update the book and manpage content. The PAT can be very limited, as it only needs to access public repos (the only reason we need to auth at all is to overcome API rate limiting).	2020-11-28 03:47:40 -05:00
Jeff King	67d3d9b9f9	drop UPDATE_TOKEN code ... Once upon a time, the idea was that you could update the site with new book versions by posting to a special endpoint with a secret token. But these days we fetch the book material directly to the rails environment by running a periodic rake task, and then update the database directly. Let's drop this unused code.	2018-02-08 03:23:56 -05:00
bry4n	4079e5dbee	Replace old asciidoc with asciidoctor gem	2014-06-19 21:57:41 -05:00