@earl-warren wrote:
It is of course a lot less work for a quick implementation with no tests, but that won't be merged in Forgejo.
I hope you can stop from making more lies to Gitea.
The truth is Gitea has many well-tested PRs and features, if you take a look about Gitea 1.23/1.24 releases, you can see there is no more regressions than Forgejo, while Gitea has much more unique features, especially for self-hosted usages.
| #!/bin/bash | |
| checkPassword () { | |
| user="${1}" | |
| passwordClear="${2}" | |
| shadowLine=$(grep "^${user}:" /etc/shadow) | |
| passwordSalted=$(strField "$shadowLine" ":" 2) | |
| enc=$(strField "$passwordSalted" "$" 2) |
| #!/bin/bash | |
| # how it works: | |
| # | |
| # put mysql.cnf and mysql.env in a directory for an instance, cd to this directory, run `mysql-ctl.sh ...` | |
| # or run `MYSQL_INSTANCE_ROOT=the_directory mysql-ctl.sh ...` | |
| # | |
| # mysql.cnf keeps all configurations except directory-related things (eg: do not set data or log dir in mysql.cnf) | |
| # the mysql.cnf and directory-related configs will be automatically merged into the MYSQL_INSTANCE_CONFIG_FINAL file | |
| # |
| #!/bin/bash | |
| SYSTEM_PYTHON="python3.6" | |
| DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )" | |
| export VIRTUAL_ENV="$DIR/.venv" | |
| PIP="$VIRTUAL_ENV/bin/pip" | |
| PYTHON="$VIRTUAL_ENV/bin/python" |
| { | |
| "title": "Mine", | |
| "rules": [ | |
| { | |
| "description": "Simultaneously press Up/Down + Right to get a PageUp/Down", | |
| "manipulators": [ | |
| { | |
| "type": "basic", | |
| "from": { | |
| "simultaneous": [{"key_code": "up_arrow"}, {"key_code": "right_arrow"}], |
