blog
blog
github issues
可以用issues来写blog 优点:
- 支持回复
- 支持tag
- 可以计划
- 支持订阅
- 全文检索
缺点:
- 任何人都可以新建issue(有好处也有不好的)
感觉很棒
设计
- a 提供api供其它服务调用的方式来操作issue
- b 提供MQ消费者的方式来操作issue
- c 提供定时任务来操作issue
思考
直接创建一个网站首页
获取api显示
https://api.github.com/repos/lzh2nix/articles/issues?page=2 在上面的api header中有以下信息 link: https://api.github.com/repositories/112858035/issues?page=1; rel="prev", https://api.github.com/repositories/112858035/issues?page=3; rel="next", https://api.github.com/repositories/112858035/issues?page=3; rel="last", https://api.github.com/repositories/112858035/issues?page=1; rel="first"
https://github.com/josegonzalez/python-github-backup
https://github.com/IQAndreas/github-issues-import
https://github.com/devspace/awesome-github-templates
gitee 也有对应的api:https://gitee.com/api/v5/swagger#/getV5ReposOwnerRepoIssuesComments
开发一个同步工具
利用issues的api
评论可以单向同步到自己的blog系统
提高 API 访问次数的配额
默认情况下你是用匿名权限访问 github 接口的, github 的访问限制是一个小时最多 60 次请求,这显然是不够的,如何提高限制呢?
-
到个人设置下的 Personal access tokens 页(https://github.com/settings/tokens ),如下图,点击右上角的 Generate new token
-
填写名称,只勾选 public_repo,然后保存,github 会生成一个可访问你公开项目的 access_token,将它填入到配置文件的 access_token 的值中,并取消注释。
-
打开 app.js,取消掉第 17 行和 88 行的注释,保存后重新上传即可
data:{ // access_token:_config['access_token'] },
python setup.py check
python setup.py sdist bdist_wheel
python setup.py install
twine upload dist/*
python -m iblog -h
or
iblog -h
Metadata
Release files for iblog 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| iblog-0.0.6.tar.gz | 4.8 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iblog-0.0.6-py3.7.egg | Legacy Egg format | - | - | Details |
| iblog-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.0 kB
Release files / iblog-0.0.6.tar.gz
| Download URL | iblog-0.0.6.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c6f21273bd9155c1b3e0cb33cb8b0ab04dca93f6ea41b726ce4140674e790fb
|
|
BLAKE2b-256 checksum How to use checksums |
46becfa636191c8de424d916da57e9a00710984b59e3359b6354ba040a398e04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0.post20200714 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.3
|
Release files / iblog-0.0.6-py3.7.egg
| Download URL | iblog-0.0.6-py3.7.egg |
|---|---|
| Size | 10.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
f8c8c19fa00de197d6398ab2d0007467e6164a6cc0bd0fba1d4a84d5cacc9063
|
|
BLAKE2b-256 checksum How to use checksums |
b15f25087dd1478ff1ad463f3ee80d6a04aef851a0795b60c07e941db8e7fc07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0.post20200714 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.3
|
Release files / iblog-0.0.6-py3-none-any.whl
| Download URL | iblog-0.0.6-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cbbeb71c8227da83d50358b0f34842af10fa4d37ea838dc2d021abeef221a53b
|
|
BLAKE2b-256 checksum How to use checksums |
637e3d5a7271bc3a957180f69f4bc6cdc906ccbae4ed54ec0ee103306d5bfa20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0.post20200714 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.3
|
Security for iblog 0.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.