Upload Modules

This commit is contained in:
mxd
2026-05-17 11:34:54 +08:00
commit 9f28fed00a
171 changed files with 53743 additions and 0 deletions

View File

@@ -0,0 +1,46 @@
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment include:
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at winshining@163.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/

View File

@@ -0,0 +1,41 @@
## Guidelines to contribute
#### **When you find a bug**
* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/winshining/nginx-http-flv-module/issues).
* If there is no issue addressing the problem, [open a new one](https://github.com/winshining/nginx-http-flv-module/issues/new). Be sure to include a **title prefixed by '[bug]' and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
#### **Write a patch that fixes a bug**
* Open a new GitHub pull request with the patch.
* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
* Before submitting, be sure the commit description is prefixed by:
* **[add]** if new features were added.
* **[dev]** if codes were changed.
* **[fix]** if bugs were fixed.
* **[misc]** if some changes were done and bugs were fixed.
* Ensure that your codes conform to code conventions:
* All files are prefixed by 'ngx\_'.
* Include #ifndef \_FILE\_NAME\_H\_INCLUDED\_, #define \_FILE\_NAME\_H\_INCLUDED\_ and #endif in header files.
* Comments use /* ... */ are preferable.
* It would be better that built-in types appear before customized types.
* There should be no less than 2 spaces between types and variables.
* Variables are aligned by character, not '\*'.
* No more than 80 characters in a single code or comment line.
* Two blank lines between two functions, styles of macro and type definitions are same as functions.
#### **Add a new feature or change an existing one**
* Open an issue on GitHub prefixed by '[feature]' until you have collected positive feedback about the change.
#### **Questions about the source code**
* Open an issue on GitHub prefixed by '[misc]', describe as clear as possible.
Thanks!
Winshining

View File

@@ -0,0 +1 @@
custom: ['https://www.paypal.me/ShingWong']

View File

@@ -0,0 +1,14 @@
When you meet a bug, please open the issue including a title prefixed by '[bug]' and describe it as follows:
(当你碰到一个 bug请在提出问题时以 '[bug]' 为前缀写明标题,并且像下面的内容一样描述它):
### Expected behavior (期望行为)
### Actual behavior (实际行为)
### OS and Nginx version (操作系统和 Nginx 版本号)
### Configuration file (配置文件)
### Steps to reproduce the behavior (复现问题步骤)
### Error log if any (错误日志)

View File

@@ -0,0 +1,42 @@
name: nginx-http-flv-module CI
on:
push:
branches: [ "master" ]
pull_request:
branches: [ "master" ]
jobs:
build:
runs-on: ubuntu-latest
env:
NGINX_VERSION: nginx-1.28.0
steps:
- uses: actions/checkout@v3
- name: download nginx
working-directory: ../
run: wget https://nginx.org/download/${{env.NGINX_VERSION}}.tar.gz
- name: uncompress nginx
working-directory: ../
run: tar zxvf ${{env.NGINX_VERSION}}.tar.gz
- name: configure (build into nginx)
working-directory: ../${{env.NGINX_VERSION}}
run: ./configure --add-module=../nginx-http-flv-module
- name: make
working-directory: ../${{env.NGINX_VERSION}}
run: make
- name: clean
working-directory: ../${{env.NGINX_VERSION}}
run: make clean
- name: configure (build as a dynamic module)
working-directory: ../${{env.NGINX_VERSION}}
run: ./configure --add-dynamic-module=../nginx-http-flv-module
- name: make
working-directory: ../${{env.NGINX_VERSION}}
run: make
- name: remove
working-directory: ../
run: rm -rf "${{env.NGINX_VERSION}}*"