Sphinx official quick start guide
https://www.sphinx-doc.org/en/master/usage/quickstart.html
reStructuredText Primer
https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html
| /** | |
| * 更新日期:2024-04-05 15:30:15 | |
| * 用法:Sub-Store 脚本操作添加 | |
| * rename.js 以下是此脚本支持的参数,必须以 # 为开头多个参数使用"&"连接,参考上述地址为例使用参数。 禁用缓存url#noCache | |
| * | |
| *** 主要参数 | |
| * [in=] 自动判断机场节点名类型 优先级 zh(中文) -> flag(国旗) -> quan(英文全称) -> en(英文简写) | |
| * 如果不准的情况, 可以加参数指定: | |
| * | |
| * [nm] 保留没有匹配到的节点 |
Sphinx official quick start guide
https://www.sphinx-doc.org/en/master/usage/quickstart.html
reStructuredText Primer
https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html
目前API路由非常混乱,产生安全性问题、性能问题等,也为了实现有效的前后端分离,需要大规模重构。
这里先预留一个位置,之后有空了编辑。
我想了一下最可能造成此次锁表的原因。你是程序在线的时候执行的knex-migrate up吗?那样这次是有可能锁死。
如果你cherry-pick了 935681b14f4f41a6af27977d5cc1cae6c2f5817a
这个是为了解决之前打错字的情况,也为了这次你执行knex-migrate up能正确运行而不至于直接挂在前面的错误文件上。
当你执行knex-migrate的时候,它会读取knex_migrations表,对比没有执行过的migration文件,然后执行并把完成的migration记录文件名到这个表里面。
也就是说本次你应该是看到执行了两个migration:
20210223200240_drop_not_null_constraints.js
20210304101412_fix_view_userMetatdata.js
This focuses on generating the certificates for loading local virtual hosts hosted on your computer, for development only.
Do not use self-signed certificates in production ! For online certificates, use Let's Encrypt instead (tutorial).
| // Website you intended to retrieve for users. | |
| //const upstream = 'www.google.com' | |
| const upstream = '5a1eddaec0e1.ngrok.io' | |
| // Custom pathname for the upstream website. | |
| const upstream_path = '/' | |
| // Website you intended to retrieve for users using mobile devices. | |
| //const upstream_mobile = 'www.google.com' | |
| const upstream_mobile = '5a1eddaec0e1.ngrok.io' |
| // DO Spaces isn't handling OPTIONS properly so I am manually setting them. It does not affect user experience, though. | |
| // For DO Spaces, if Origin header is not set, DO won't return CORS headers at all. Must be set in the worker. | |
| // Other references: | |
| // https://community.cloudflare.com/t/injecting-cors-headers-in-response-larger-requests-fail/98479/7 | |
| // https://www.digitalocean.com/community/questions/setting-access-control-allow-origin-in-my-space-doesn-t-work-with | |
| addEventListener('fetch', event => { | |
| event.respondWith(handleRequest(event.request)) | |
| }) |
.notification .status__avatar::before,
.notification .status__avatar::after {
display: none !important;
}
.status__wrapper .status:first-child .status__avatar::before,
.status__wrapper .status:first-child .status__avatar::after,
.entry.h-entry .status__avatar div::before,
.entry.h-entry .status__avatar div::after,version: 2
aliases:
- &defaults
docker:
- image: circleci/ruby:2.7-buster-node
environment: &ruby_environment
BUNDLE_JOBS: 3
BUNDLE_RETRY: 3