feat: 修改一些应用的 README.md (#141)

This commit is contained in:
zhengkunwang223 2023-06-06 11:06:33 +08:00 committed by GitHub
parent ebba7a4ecd
commit c581343a1f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 120 additions and 498 deletions

View File

@ -93,42 +93,13 @@
<https://alist.nn.ci/zh/> <https://alist.nn.ci/zh/>
## Demo ## 使用
在容器中执行 ./alist admin 获取密码
<https://al.nn.ci>
## 讨论 ## 讨论
一般问题请到[讨论论坛](https://github.com/Xhofe/alist/discussions) **issue仅针对错误报告和功能请求。** 一般问题请到[讨论论坛](https://github.com/Xhofe/alist/discussions) **issue仅针对错误报告和功能请求。**
## 赞助
AList 是一个开源软件如果你碰巧喜欢这个项目并希望我继续下去请考虑赞助我或提供一个单一的捐款感谢所有的爱和支持https://alist.nn.ci/zh/guide/sponsor.html
### 特别赞助
- [找资源 - 阿里云盘资源搜索引擎](https://zhaoziyuan.la/)
- [KinhDown 百度云盘不限速下载永久免费已稳定运行3年非常可靠Q群 -> 786799372](https://kinhdown.com)
- [JetBrains: Essential tools for software developers and teams](https://www.jetbrains.com/)
## 贡献者
Thanks goes to these wonderful people:
[![Contributors](http://contributors.nn.ci/api?repo=alist-org/alist&repo=alist-org/alist-web&repo=alist-org/docs)](https://github.com/alist-org/alist/graphs/contributors)
## 许可
`AList` 是在 AGPL-3.0 许可下许可的开源软件。
## 免责声明
- 本程序为免费开源项目旨在分享网盘文件方便下载以及学习golang使用时请遵守相关法律法规请勿滥用
- 本程序通过调用官方sdk/接口实现,无破坏官方接口行为;
- 本程序仅做302重定向/流量转发,不拦截、存储、篡改任何用户数据;
- 在使用本程序之前你应了解并承担相应的风险包括但不限于账号被ban下载限速等与本程序无关
- 如有侵权,请通过[邮件](mailto:i@nn.ci)与我联系,会及时处理。
---
> [@博客](https://nn.ci/) · [@GitHub](https://github.com/Xhofe) · [@Telegram群](https://t.me/alist_chat) · [@Discord](https://discord.gg/F4ymsH4xv2)

View File

@ -1,73 +1,13 @@
# Distribution # docker-registry
The toolset to pack, ship, store, and deliver content. **docker-registry** 是一个开源的镜像仓库,用于存储和管理 Docker 镜像。它允许您在 Linux 服务器上创建私有的 Docker 镜像仓库,以便团队成员共享和访问镜像。
This repository's main product is the Open Source Registry implementation docker-registry 的特点包括:
for storing and distributing container images using the
[OCI Distribution Specification](https://github.com/opencontainers/distribution-spec).
The goal of this project is to provide a simple, secure, and scalable base
for building a large scale registry solution or running a simple private registry.
It is a core library for many registry operators including Docker Hub, GitHub Container Registry,
GitLab Container Registry and DigitalOcean Container Registry, as well as the CNCF Harbor
Project, and VMware Harbor Registry.
<img src="/distribution-logo.svg" width="200px" /> - **镜像存储和管理**docker-registry 提供了功能强大的仓库系统,用于存储和管理 Docker 镜像,方便团队成员之间的共享和访问。
- **私有化部署**:您可以在自己的 Linux 服务器上搭建私有的 docker-registry以满足安全和隐私要求。
- **访问控制**docker-registry 支持设置访问权限,可以控制谁可以拉取和推送镜像,以保护您的镜像和数据的安全性。
- **标签和版本管理**:您可以为镜像设置标签和版本,方便对镜像进行分类和管理。
- **兼容性**docker-registry 兼容 Docker 镜像仓库的标准 API您可以使用 Docker CLI 或其他 Docker 客户端工具与之交互。
[![Build Status](https://github.com/distribution/distribution/workflows/CI/badge.svg?branch=main&event=push)](https://github.com/distribution/distribution/actions?query=workflow%3ACI) 使用 docker-registry您可以轻松地构建、存储和管理自己的 Docker 镜像为团队成员提供方便的访问和共享渠道。无论是个人项目还是团队开发docker-registry 都是一个强大的工具,帮助您更好地利用 Docker 技术。
[![GoDoc](https://img.shields.io/badge/go.dev-reference-007d9c?logo=go&logoColor=white&style=flat-square)](https://pkg.go.dev/github.com/distribution/distribution)
[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
[![codecov](https://codecov.io/gh/distribution/distribution/branch/main/graph/badge.svg)](https://codecov.io/gh/distribution/distribution)
[![FOSSA Status](https://app.fossa.com/api/projects/custom%2B162%2Fgithub.com%2Fdistribution%2Fdistribution.svg?type=shield)](https://app.fossa.com/projects/custom%2B162%2Fgithub.com%2Fdistribution%2Fdistribution?ref=badge_shield)
[![OCI Conformance](https://github.com/distribution/distribution/workflows/conformance/badge.svg)](https://github.com/distribution/distribution/actions?query=workflow%3Aconformance)
This repository contains the following components:
|**Component** |Description |
|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **registry** | An implementation of the [OCI Distribution Specification](https://github.com/opencontainers/distribution-spec). |
| **libraries** | A rich set of libraries for interacting with distribution components. Please see [godoc](https://pkg.go.dev/github.com/distribution/distribution) for details. **Note**: The interfaces for these libraries are **unstable**. |
| **documentation** | Docker's full documentation set is available at [docs.docker.com](https://docs.docker.com). This repository [contains the subset](docs/) related just to the registry. |
### How does this integrate with Docker, containerd, and other OCI client?
Clients implement against the OCI specification and communicate with the
registry using HTTP. This project contains a client implementation which
is currently in use by Docker, however, it is deprecated for the
[implementation in containerd](https://github.com/containerd/containerd/tree/master/remotes/docker)
and will not support new features.
### What are the long term goals of the Distribution project?
The _Distribution_ project has the further long term goal of providing a
secure tool chain for distributing content. The specifications, APIs and tools
should be as useful with Docker as they are without.
Our goal is to design a professional grade and extensible content distribution
system that allow users to:
* Enjoy an efficient, secured and reliable way to store, manage, package and
exchange content
* Hack/roll their own on top of healthy open-source components
* Implement their own home made solution through good specs, and solid
extensions mechanism.
## Contribution
Please see [CONTRIBUTING.md](CONTRIBUTING.md) for details on how to contribute
issues, fixes, and patches to this project. If you are contributing code, see
the instructions for [building a development environment](BUILDING.md).
## Communication
For async communication and long running discussions please use issues and pull requests on the github repo.
This will be the best place to discuss design and implementation.
For sync communication we have a #distribution channel in the [CNCF Slack](https://slack.cncf.io/)
that everyone is welcome to join and chat about development.
## Licenses
The distribution codebase is released under the [Apache 2.0 license](LICENSE).
The README.md file, and files in the "docs" folder are licensed under the
Creative Commons Attribution 4.0 International License. You may obtain a
copy of the license, titled CC-BY-4.0, at http://creativecommons.org/licenses/by/4.0/.

View File

@ -1,3 +1,19 @@
# flarum
**flarum** 是一个现代化、轻量级的开源社区论坛软件。它提供了简洁而美观的用户界面,并具有丰富的功能,可用于构建和管理在线社区。
flarum 的特点包括:
- **简洁美观**flarum 的界面设计简洁、现代,提供了良好的用户体验,使用户能够轻松浏览和参与社区讨论。
- **可扩展性**flarum 支持插件系统,可以根据需要扩展功能,定制和增强社区论坛的各个方面。
- **强大的权限管理**flarum 提供了灵活的权限管理机制,允许管理员对用户、用户组、板块等进行细粒度的权限设置。
- **多语言支持**flarum 支持多种语言,可以轻松创建和管理多语言的社区论坛。
- **社交登录集成**flarum 可与社交媒体账户(如 Google、Facebook、Twitter 等)进行集成,允许用户通过其社交账户登录和参与社区。
- **响应式布局**flarum 的界面具有响应式布局,适应不同设备上的不同屏幕大小,使用户在桌面、平板和手机等设备上都能获得良好的浏览体验。
使用 flarum您可以创建一个功能强大、易于管理的在线社区论坛。不论是支持技术讨论、产品交流还是社交互动flarum 都是一个值得考虑的选择。
# 使用说明 # 使用说明
## 账户密码 ## 账户密码
- 初始账户: flarum - 初始账户: flarum
@ -24,46 +40,4 @@ php flarum cache:clear
>> - https://hub.docker.com/r/crazymax/flarum >> - https://hub.docker.com/r/crazymax/flarum
>> - https://github.com/crazy-max/docker-flarum >> - https://github.com/crazy-max/docker-flarum
# 原始相关
<p align="center">
<a href="https://flarum.org/"><img src="https://flarum.org/assets/img/logo.png"></a>
</p>
<p align="center">
<a href="https://packagist.org/packages/flarum/core"><img src="https://poser.pugx.org/flarum/core/d/total.svg" alt="Total Downloads"></a>
<a href="https://packagist.org/packages/flarum/core"><img src="https://poser.pugx.org/flarum/core/v/stable.svg" alt="Latest Stable Version"></a>
<a href="https://packagist.org/packages/flarum/core"><img src="https://poser.pugx.org/flarum/core/license.svg" alt="License"></a>
</p>
## About Flarum
**[Flarum](https://flarum.org/) is a delightfully simple discussion platform for your website.** It's fast and easy to use, with all the features you need to run a successful community. It is designed to be:
* **Fast and simple.** No clutter, no bloat, no complex dependencies. Flarum is built with PHP so its quick and easy to deploy. The interface is powered by Mithril, a performant JavaScript framework with a tiny footprint.
* **Beautiful and responsive.** This is forum software for humans. Flarum is carefully designed to be consistent and intuitive across platforms, out-of-the-box.
* **Powerful and extensible.** Customize, extend, and integrate Flarum to suit your community. Flarums architecture is amazingly flexible, with a powerful Extension API.
![screenshot](https://flarum.org/assets/img/home-screenshot.png)
## Installation
Read the **[Installation guide](https://docs.flarum.org/install)** to get started. For support, refer to the [documentation](https://docs.flarum.org/), and ask questions on the [community forum](https://discuss.flarum.org/) or [Discord chat](https://flarum.org/discord/).
## Contributing
Thank you for considering contributing to Flarum! Please read the **[Contributing guide](https://docs.flarum.org/contributing)** to learn how you can help.
This repository only holds the Flarum skeleton application. Most development happens in [flarum/core](https://github.com/flarum/core).
## Security Vulnerabilities
If you discover a security vulnerability within Flarum, please follow our [security policy](https://github.com/flarum/core/security/policy) so we can address it promptly.
## License
Flarum is open-source software licensed under the [MIT License](https://github.com/flarum/flarum/blob/master/LICENSE).

View File

@ -1,92 +1,40 @@
## Purpose <p align="center">
<a href="https://gitea.io/">
<img alt="Gitea" src="https://raw.githubusercontent.com/go-gitea/gitea/main/public/img/gitea.svg" width="220"/>
</a>
</p>
<h1 align="center">Gitea - Git with a cup of tea</h1>
The goal of this project is to make the easiest, fastest, and most ## 简介
painless way of setting up a self-hosted Git service.
As Gitea is written in Go, it works across **all** the platforms and **gitea** 是一个轻量级的自托管Git服务用于在Linux服务器上搭建私有的Git存储库和代码托管平台。它提供了一个简单易用的Web界面使您能够方便地管理和协作开发项目。
architectures that are supported by Go, including Linux, macOS, and
Windows on x86, amd64, ARM and PowerPC architectures.
You can try it out using [the online demo](https://try.gitea.io/).
This project has been
[forked](https://blog.gitea.io/2016/12/welcome-to-gitea/) from
[Gogs](https://gogs.io) since November of 2016, but a lot has changed.
## Building gitea 具有以下特点:
From the root of the source tree, run: - **轻量级**gitea 资源消耗较低,适合运行在较小的服务器上,占用的存储空间较小。
- **易于安装和部署**gitea 提供了简单的安装方法,并且可以在不同的 Linux 发行版上运行。
- **功能丰富**gitea 提供了许多功能,包括代码版本控制、问题跟踪、代码审查、维基文档、持续集成等。
- **多用户和团队支持**gitea 允许创建多个用户和组织,并为每个项目设置不同的访问权限。
- **可扩展性**gitea 支持插件系统,可以根据需要扩展功能。
TAGS="bindata" make build 使用 gitea您可以进行以下操作
or if SQLite support is required: - 创建和管理代码存储库。
- 进行代码版本控制,包括提交、分支、合并等操作。
- 跟踪和解决问题。
- 进行代码审查和合并请求。
- 创建和编辑维基文档。
- 集成持续集成和部署流程。
TAGS="bindata sqlite sqlite_unlock_notify" make build 通过 gitea 的用户友好的界面和丰富的功能,您可以轻松地进行团队协作和项目管理,提高开发效率和代码质量。
The `build` target is split into two sub-targets: 请注意,在使用 gitea 时,建议采取适当的安全措施,如设置强密码、启用双因素身份验证以及定期备份数据,以确保代码和项目的安全性和可靠性。
- `make backend` which requires [Go Stable](https://go.dev/dl/), required version is defined in [go.mod](/go.mod).
- `make frontend` which requires [Node.js LTS](https://nodejs.org/en/download/) or greater and Internet connectivity to download npm dependencies.
When building from the official source tarballs which include pre-built frontend files, the `frontend` target will not be triggered, making it possible to build without Node.js and Internet connectivity. ## 截图
Parallelism (`make -j <num>`) is not supported. |![Dashboard](https://dl.gitea.io/screenshots/home_timeline.png)|![User Profile](https://dl.gitea.io/screenshots/user_profile.png)|![Global Issues](https://dl.gitea.io/screenshots/global_issues.png)|
|:---:|:---:|:---:|
More info: https://docs.gitea.io/en-us/install-from-source/ |![Branches](https://dl.gitea.io/screenshots/branches.png)|![Web Editor](https://dl.gitea.io/screenshots/web_editor.png)|![Activity](https://dl.gitea.io/screenshots/activity.png)|
|![New Migration](https://dl.gitea.io/screenshots/migration.png)|![Migrating](https://dl.gitea.io/screenshots/migration.gif)|![Pull Request View](https://image.ibb.co/e02dSb/6.png)
## Using ![Pull Request Dark](https://dl.gitea.io/screenshots/pull_requests_dark.png)|![Diff Review Dark](https://dl.gitea.io/screenshots/review_dark.png)|![Diff Dark](https://dl.gitea.io/screenshots/diff_dark.png)|
./gitea web
NOTE: If you're interested in using our APIs, we have experimental
support with [documentation](https://try.gitea.io/api/swagger).
## Contributing
Expected workflow is: Fork -> Patch -> Push -> Pull Request
NOTES:
1. **YOU MUST READ THE [CONTRIBUTORS GUIDE](CONTRIBUTING.md) BEFORE STARTING TO WORK ON A PULL REQUEST.**
2. If you have found a vulnerability in the project, please write privately to **security@gitea.io**. Thanks!
## Translating
Translations are done through Crowdin. If you want to translate to a new language ask one of the managers in the Crowdin project to add a new language there.
You can also just create an issue for adding a language or ask on discord on the #translation channel. If you need context or find some translation issues, you can leave a comment on the string or ask on Discord. For general translation questions there is a section in the docs. Currently a bit empty but we hope to fill it as questions pop up.
https://docs.gitea.io/en-us/translation-guidelines/
[![Crowdin](https://badges.crowdin.net/gitea/localized.svg)](https://crowdin.com/project/gitea)
## Further information
For more information and instructions about how to install Gitea, please look at our [documentation](https://docs.gitea.io/en-us/).
If you have questions that are not covered by the documentation, you can get in contact with us on our [Discord server](https://discord.gg/Gitea) or create a post in the [discourse forum](https://discourse.gitea.io/).
We maintain a list of Gitea-related projects at [gitea/awesome-gitea](https://gitea.com/gitea/awesome-gitea).
The Hugo-based documentation theme is hosted at [gitea/theme](https://gitea.com/gitea/theme).
The official Gitea CLI is developed at [gitea/tea](https://gitea.com/gitea/tea).
## Authors
- [Maintainers](https://github.com/orgs/go-gitea/people)
- [Contributors](https://github.com/go-gitea/gitea/graphs/contributors)
- [Translators](options/locale/TRANSLATORS)
## FAQ
**How do you pronounce Gitea?**
Gitea is pronounced [/ɡɪti:/](https://youtu.be/EM71-2uDAoY) as in "gi-tea" with a hard g.
**Why is this not hosted on a Gitea instance?**
We're [working on it](https://github.com/go-gitea/gitea/issues/1029).
## License
This project is licensed under the MIT License.
See the [LICENSE](https://github.com/go-gitea/gitea/blob/main/LICENSE) file
for the full license text.

View File

@ -1,45 +1,36 @@
------------------------------ <p align="center">
<a href="https://halo.run" target="_blank" rel="noopener noreferrer">
<img width="100" src="https://halo.run/logo" alt="Halo logo" />
</a>
</p>
## 快速开始 <p align="center"><b>Halo</b> [ˈheɪloʊ],强大易用的开源建站工具。</p>
```bash <p align="center">
docker run \ <a href="https://github.com/halo-dev/halo/releases"><img alt="GitHub release" src="https://img.shields.io/github/release/halo-dev/halo.svg?style=flat-square&include_prereleases" /></a>
-it -d \ <a href="https://hub.docker.com/r/halohub/halo"><img alt="Docker pulls" src="https://img.shields.io/docker/pulls/halohub/halo?style=flat-square" /></a>
--name halo \ <a href="https://github.com/halo-dev/halo/commits"><img alt="GitHub last commit" src="https://img.shields.io/github/last-commit/halo-dev/halo.svg?style=flat-square" /></a>
-p 8090:8090 \ <a href="https://github.com/halo-dev/halo/actions"><img alt="GitHub Workflow Status" src="https://img.shields.io/github/actions/workflow/status/halo-dev/halo/halo.yaml?branch=main&style=flat-square" /></a>
-v ~/.halo2:/root/.halo2 \ <a href="https://codecov.io/gh/halo-dev/halo"><img alt="Codecov percentage" src="https://img.shields.io/codecov/c/github/halo-dev/halo/main?style=flat-square&token=YsRUg9fall"/></a>
halohub/halo:2.6.0 \ <br />
--halo.external-url=http://localhost:8090/ \ <a href="https://halo.run">官网</a>
--halo.security.initializer.superadminusername=admin \ <a href="https://docs.halo.run">文档</a>
--halo.security.initializer.superadminpassword=P@88w0rd <a href="https://bbs.halo.run">社区</a>
``` <a href="https://gitee.com/halo-dev">Gitee</a>
<a href="https://t.me/halo_dev">Telegram 频道</a>
</p>
以上仅作为体验使用,详细部署文档请查阅:<https://docs.halo.run/getting-started/install/docker-compose> # halo
## 在线体验 **halo** 是一个简洁、高效的开源博客平台。它提供了易于使用的界面和丰富的功能,使用户可以轻松地创建个人博客或专业网站。
- 环境地址:<https://demo.halo.run> halo 的特点包括:
- 后台地址:<https://demo.halo.run/console>
- 用户名:`demo`
- 密码:`P@ssw0rd123..`
## 生态 - **简洁易用**halo 的界面设计简洁清晰,使用户能够快速上手并轻松管理博客内容。
- **高度可定制**halo 提供了丰富的主题和插件系统,用户可以根据自己的需求选择合适的主题和插件,定制博客的外观和功能。
- **多媒体支持**halo 支持插入和管理多媒体内容,如图片、视频和音频,使博客内容更加丰富和生动。
- **多语言支持**halo 支持多种语言,可以创建和管理多语言的博客内容,满足全球用户的需求。
- **SEO友好**halo 内置了优化的SEO功能帮助您提升博客在搜索引擎中的排名增加曝光和访问量。
- **安全可靠**halo 针对安全性进行了严格设计和测试,保护博客数据的安全和可靠性。
可访问 [awesome-halo](https://github.com/halo-sigs/awesome-halo) 查看已经适用于 Halo 2.0 的主题和插件,以及适用于 Halo 使用 halo您可以轻松地撰写和发布博客文章与读者分享知识和经验。无论是个人博客、技术博客还是专业网站halo 都是一个强大的工具,助您构建出优秀的在线内容平台。
1.x 的相关仓库。
## 许可证
[![license](https://img.shields.io/github/license/halo-dev/halo.svg?style=flat-square)](https://github.com/halo-dev/halo/blob/master/LICENSE)
Halo 使用 GPL-v3.0 协议开源,请遵守开源协议。
## 贡献
参考 [CONTRIBUTING](https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md)。
<a href="https://github.com/halo-dev/halo/graphs/contributors"><img src="https://opencollective.com/halo/contributors.svg?width=890&button=false" /></a>
## 状态
![Repobeats analytics](https://repobeats.axiom.co/api/embed/ad008b2151c22e7cf734d2688befaa795d593b95.svg "Repobeats analytics image")

View File

@ -43,134 +43,20 @@
</a> </a>
</p> </p>
--- # Jellyfin
Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it. We welcome anyone who is interested in joining us in our quest! **Jellyfin** 是一个免费开源的媒体服务器软件,用于组织、管理和流媒体共享您的音频、视频和图片等媒体内容。
For further details, please see [our documentation page](https://jellyfin.org/docs/). To receive the latest updates, get help with Jellyfin, and join the community, please visit [one of our communication channels](https://jellyfin.org/docs/general/getting-help). For more information about the project, please see our [about page](https://jellyfin.org/docs/general/about). Jellyfin 的特点包括:
<strong>Want to get started?</strong><br/> - **个人媒体中心**Jellyfin 允许您将自己的媒体文件整理成库,创建个人的媒体中心,以便随时访问和播放您的音乐、电影、电视节目等。
Check out our <a href="https://jellyfin.org/downloads">downloads page</a> or our <a href="https://jellyfin.org/docs/general/installation/">installation guide</a>, then see our <a href="https://jellyfin.org/docs/general/quick-start">quick start guide</a>. You can also <a href="https://jellyfin.org/docs/general/installation/source">build from source</a>.<br/> - **跨平台支持**Jellyfin 可以在多种平台上运行,包括 Linux、Windows、macOS、FreeBSD 等,使您可以在不同设备和操作系统上使用它。
- **多设备访问**:通过 Jellyfin 的用户友好的界面和各种客户端应用程序,您可以从任何设备(如电脑、手机、平板)上访问和流媒体您的媒体内容。
- **共享和远程访问**Jellyfin 允许您与家人、朋友共享媒体内容,并支持通过互联网远程访问您的库,让您随时随地享受媒体娱乐。
- **媒体转码和流媒体**Jellyfin 能够自动转码和流媒体您的媒体内容,以适应不同设备和网络条件,确保您的媒体内容的最佳播放体验。
<strong>Something not working right?</strong><br/> 使用 Jellyfin您可以轻松地构建自己的媒体服务器将音频、视频和图片等媒体内容整理和共享随时享受高质量的媒体娱乐体验。
Open an <a href="https://jellyfin.org/docs/general/contributing/issues">Issue</a> on GitHub.<br/>
<strong>Want to contribute?</strong><br/> 请注意,使用 Jellyfin 时,请遵守您所在地区的版权和法律规定,合法地使用和共享媒体内容。
Check out our <a href="https://jellyfin.org/contribute">contributing choose-your-own-adventure</a> to see where you can help, then see our <a href="https://jellyfin.org/docs/general/contributing/">contributing guide</a> and our <a href="https://jellyfin.org/docs/general/community-standards">community standards</a>.<br/>
<strong>New idea or improvement?</strong><br/>
Check out our <a href="https://features.jellyfin.org/?view=most-wanted">feature request hub</a>.<br/>
<strong>Don't see Jellyfin in your language?</strong><br/>
Check out our <a href="https://translate.jellyfin.org">Weblate instance</a> to help translate Jellyfin and its subprojects.<br/>
<a href="https://translate.jellyfin.org/engage/jellyfin/?utm_source=widget">
<img src="https://translate.jellyfin.org/widgets/jellyfin/-/jellyfin-web/multi-auto.svg" alt="Detailed Translation Status"/>
</a>
---
## Jellyfin Server
This repository contains the code for Jellyfin's backend server. Note that this is only one of many projects under the Jellyfin GitHub [organization](https://github.com/jellyfin/) on GitHub. If you want to contribute, you can start by checking out our [documentation](https://jellyfin.org/docs/general/contributing/index.html) to see what to work on.
## Server Development
These instructions will help you get set up with a local development environment in order to contribute to this repository. Before you start, please be sure to completely read our [guidelines on development contributions](https://jellyfin.org/docs/general/contributing/development.html). Note that this project is supported on all major operating systems except FreeBSD, which is still incompatible.
### Prerequisites
Before the project can be built, you must first install the [.NET 7.0 SDK](https://dotnet.microsoft.com/download/dotnet) on your system.
Instructions to run this project from the command line are included here, but you will also need to install an IDE if you want to debug the server while it is running. Any IDE that supports .NET 6 development will work, but two options are recent versions of [Visual Studio](https://visualstudio.microsoft.com/downloads/) (at least 2022) and [Visual Studio Code](https://code.visualstudio.com/Download).
[ffmpeg](https://github.com/jellyfin/jellyfin-ffmpeg) will also need to be installed.
### Cloning the Repository
After dependencies are installed you will need to clone a local copy of this repository. If you just want to run the server from source you can clone this repository directly, but if you are intending to contribute code changes to the project, you should [set up your own fork](https://jellyfin.org/docs/general/contributing/development.html#set-up-your-copy-of-the-repo) of the repository. The following example shows how you can clone the repository directly over HTTPS.
```bash
git clone https://github.com/jellyfin/jellyfin.git
```
### Installing the Web Client
The server is configured to host the static files required for the [web client](https://github.com/jellyfin/jellyfin-web) in addition to serving the backend by default. Before you can run the server, you will need to get a copy of the web client since they are not included in this repository directly.
Note that it is also possible to [host the web client separately](#hosting-the-web-client-separately) from the web server with some additional configuration, in which case you can skip this step.
There are three options to get the files for the web client.
1. Download one of the finished builds from the [Azure DevOps pipeline](https://dev.azure.com/jellyfin-project/jellyfin/_build?definitionId=27). You can download the build for a specific release by looking at the [branches tab](https://dev.azure.com/jellyfin-project/jellyfin/_build?definitionId=27&_a=summary&repositoryFilter=6&view=branches) of the pipelines page.
2. Build them from source following the instructions on the [jellyfin-web repository](https://github.com/jellyfin/jellyfin-web)
3. Get the pre-built files from an existing installation of the server. For example, with a Windows server installation the client files are located at `C:\Program Files\Jellyfin\Server\jellyfin-web`
### Running The Server
The following instructions will help you get the project up and running via the command line, or your preferred IDE.
#### Running With Visual Studio
To run the project with Visual Studio you can open the Solution (`.sln`) file and then press `F5` to run the server.
#### Running With Visual Studio Code
To run the project with Visual Studio Code you will first need to open the repository directory with Visual Studio Code using the `Open Folder...` option.
Second, you need to [install the recommended extensions for the workspace](https://code.visualstudio.com/docs/editor/extension-gallery#_recommended-extensions). Note that extension recommendations are classified as either "Workspace Recommendations" or "Other Recommendations", but only the "Workspace Recommendations" are required.
After the required extensions are installed, you can run the server by pressing `F5`.
#### Running From The Command Line
To run the server from the command line you can use the `dotnet run` command. The example below shows how to do this if you have cloned the repository into a directory named `jellyfin` (the default directory name) and should work on all operating systems.
```bash
cd jellyfin # Move into the repository directory
dotnet run --project Jellyfin.Server --webdir /absolute/path/to/jellyfin-web/dist # Run the server startup project
```
A second option is to build the project and then run the resulting executable file directly. When running the executable directly you can easily add command line options. Add the `--help` flag to list details on all the supported command line options.
1. Build the project
```bash
dotnet build # Build the project
cd Jellyfin.Server/bin/Debug/net7.0 # Change into the build output directory
```
2. Execute the build output. On Linux, Mac, etc. use `./jellyfin` and on Windows use `jellyfin.exe`.
### Running The Tests
This repository also includes unit tests that are used to validate functionality as part of a CI pipeline on Azure. There are several ways to run these tests.
1. Run tests from the command line using `dotnet test`
2. Run tests in Visual Studio using the [Test Explorer](https://docs.microsoft.com/en-us/visualstudio/test/run-unit-tests-with-test-explorer)
3. Run individual tests in Visual Studio Code using the associated [CodeLens annotation](https://github.com/OmniSharp/omnisharp-vscode/wiki/How-to-run-and-debug-unit-tests)
### Advanced Configuration
The following sections describe some more advanced scenarios for running the server from source that build upon the standard instructions above.
#### Hosting The Web Client Separately
It is not necessary to host the frontend web client as part of the backend server. Hosting these two components separately may be useful for frontend developers who would prefer to host the client in a separate webpack development server for a tighter development loop. See the [jellyfin-web](https://github.com/jellyfin/jellyfin-web#getting-started) repo for instructions on how to do this.
To instruct the server not to host the web content, there is a `nowebclient` configuration flag that must be set. This can specified using the command line
switch `--nowebclient` or the environment variable `JELLYFIN_NOWEBCONTENT=true`.
Since this is a common scenario, there is also a separate launch profile defined for Visual Studio called `Jellyfin.Server (nowebcontent)` that can be selected from the 'Start Debugging' dropdown in the main toolbar.
**NOTE:** The setup wizard can not be run if the web client is hosted separately.
---
<p align="center">
This project is supported by:
<br/>
<br/>
<a href="https://www.digitalocean.com"><img src="https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/SVG/DO_Logo_horizontal_blue.svg" height="50px" alt="DigitalOcean"></a>
&nbsp;
<a href="https://www.jetbrains.com"><img src="https://gist.githubusercontent.com/anthonylavado/e8b2403deee9581e0b4cb8cd675af7db/raw/fa104b7d73f759d7262794b94569f1b89df41c0b/jetbrains.svg" height="50px" alt="JetBrains logo"></a>
</p>

View File

@ -12,64 +12,17 @@
[![Docker Pulls](https://img.shields.io/docker/pulls/jenkins/jenkins.svg)](https://hub.docker.com/r/jenkins/jenkins/) [![Docker Pulls](https://img.shields.io/docker/pulls/jenkins/jenkins.svg)](https://hub.docker.com/r/jenkins/jenkins/)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/3538/badge)](https://bestpractices.coreinfrastructure.org/projects/3538) [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/3538/badge)](https://bestpractices.coreinfrastructure.org/projects/3538)
In a nutshell, Jenkins is the leading open-source automation server.
Built with Java, it provides over 1,800 [plugins](https://plugins.jenkins.io/) to support automating virtually anything,
so that humans can spend their time doing things machines cannot.
# What to Use Jenkins for and When to Use It **Jenkins** 是一个开源的自动化服务器软件用于实现持续集成和持续交付CI/CD流程。它提供了强大的工具和插件来帮助开发团队自动构建、测试和部署软件。
Use Jenkins to automate your development workflow, so you can focus on work that matters most. Jenkins is commonly used for: Jenkins 的特点包括:
- Building projects - **持续集成**Jenkins 支持自动构建和集成代码,确保团队成员的改动被及时合并和测试,减少代码冲突和集成问题。
- Running tests to detect bugs and other issues as soon as they are introduced - **自动化测试**Jenkins 提供了广泛的测试工具和插件,可以自动运行单元测试、集成测试、端到端测试等,确保软件质量和稳定性。
- Static code analysis - **自动化部署**Jenkins 可以与各种部署工具和平台集成,自动化软件的部署和发布过程,实现快速、可靠的交付。
- Deployment - **可扩展性**Jenkins 拥有丰富的插件生态系统,可以根据需求扩展和定制功能,满足不同项目和团队的需求。
- **易于配置和管理**Jenkins 提供了用户友好的界面和脚本化配置选项,使管理员能够轻松配置和管理 Jenkins 实例。
Execute repetitive tasks, save time, and optimize your development process with Jenkins. 使用 Jenkins开发团队可以实现持续集成和持续交付的最佳实践提高软件开发过程的效率和质量。无论是小型项目还是大型企业级应用Jenkins 都是一个强大而可靠的自动化服务器工具。
# Downloads 请注意Jenkins 是一个自由开源的项目,您可以从官方网站下载并自行部署和使用。
The Jenkins project provides official distributions as WAR files, Docker images, native packages and installers for platforms including several Linux distributions and Windows.
See the [Downloads](https://www.jenkins.io/download) page for references.
For all distributions Jenkins offers two release lines:
- [Weekly](https://www.jenkins.io/download/weekly/) -
Frequent releases which include all new features, improvements, and bug fixes.
- [Long-Term Support (LTS)](https://www.jenkins.io/download/lts/) -
Older release line which gets periodically updated via bug fix backports.
Latest releases:
[![Jenkins Regular Release](https://img.shields.io/endpoint?url=https%3A%2F%2Fwww.jenkins.io%2Fchangelog%2Fbadge.json)](https://www.jenkins.io/changelog)
[![Jenkins LTS Release](https://img.shields.io/endpoint?url=https%3A%2F%2Fwww.jenkins.io%2Fchangelog-stable%2Fbadge.json)](https://www.jenkins.io/changelog-stable)
# Source
Our latest and greatest source of Jenkins can be found on [GitHub](https://github.com/jenkinsci/jenkins). Fork us!
# Contributing to Jenkins
Follow the [contributing guidelines](CONTRIBUTING.md) if you want to propose a change in the Jenkins core.
For more information about participating in the community and contributing to the Jenkins project,
see [this page](https://www.jenkins.io/participate/).
Documentation for Jenkins core maintainers is in the [maintainers guidelines](docs/MAINTAINERS.adoc).
# News and Website
All information about Jenkins can be found on our [website](https://www.jenkins.io/).
Follow us on [Twitter](https://twitter.com/jenkinsci) or [LinkedIn](https://www.linkedin.com/company/jenkins-project/).
# Governance
See the [Jenkins Governance Document](https://www.jenkins.io/project/governance/) for information about the project's open governance, our philosophy and values, and development practices.
Jenkins Code of Conduct can be found [here](https://www.jenkins.io/project/conduct/).
# Adopters
Jenkins is used by millions of users and thousands of companies.
See [adopters](https://www.jenkins.io/project/adopters/) for the list of Jenkins adopters and their success stories.
# License
Jenkins is **licensed** under the **[MIT License](https://github.com/jenkinsci/jenkins/blob/master/LICENSE.txt)**.

View File

@ -9,61 +9,20 @@
--- ---
- [Change log](./ChangeLog.md) # Kodbox
- [English Document](http://kodcloud.com#lang=en)
- [中文文档](http://kodcloud.com/#lang=zh_CN) **Kodbox** 是一个开源的在线文件管理器,提供了方便的文件浏览、上传、下载和共享功能。它可以让您通过 web 浏览器访问和管理您的文件,无论是个人使用还是团队协作都非常便捷。
- [Donate](https://www.paypal.me/kalcaddle)
Kodbox 的特点包括:
- **直观友好的界面**Kodbox 提供了直观简洁的用户界面,使您可以轻松地浏览和管理文件,无需复杂的配置和学习曲线。
- **强大的文件管理功能**Kodbox 支持文件的上传、下载、复制、剪切、重命名和删除等常用操作,方便您对文件进行管理和整理。
- **文件共享和协作**Kodbox 允许您通过链接或密码共享文件,方便与他人进行文件共享和协作,提高团队工作效率。
- **多种文件预览模式**Kodbox 支持多种文件预览模式,包括文本预览、图片预览、音频预览和视频预览等,方便快速查看文件内容。
- **权限管理**Kodbox 支持对文件和文件夹设置权限,您可以控制谁可以访问、编辑或共享您的文件,保护您的文件安全和隐私。
- **插件扩展**Kodbox 提供了丰富的插件系统,允许您根据需要添加额外的功能和扩展,满足个性化的文件管理需求。
使用 Kodbox您可以随时随地通过浏览器访问和管理您的文件方便地进行文件共享和团队协作。无论是个人使用还是企业部署Kodbox 都是一个实用且可靠的在线文件管理工具。
# Features
- Use experience like operating system, Rich context menu and toolbar, drag and drop, shortcut keys......
- Available in more than 40 languages.
- File Manage
- All operations with files and folders on a remote server(copy,cute,paste,move,remove,upload,create folder/file,rename,etc.)
- Multi-User support,custom role group.
- Flexible configuration of access rights,file types restriction, user - interface and other
- Clipboard: copy, cut, paste, clear
- Selectable files & folders support (mouse click & Ctrl & Shift & words & Keyboard shortcuts)
- Keyboard shortcuts: delete deletion, ctrl+A select, ctrl+C replication, ctrl+X splicing, up/down/left/right/home/end etc.
- Multiple actions support for selected files & folders: move,copy,cute,remove,rename,open,archive,delete,download etc.
- Double or single click setup to open files & folders
- Filetree: allow to open and display multiple subfolders at a time
- Implemented natural sorting on the client-side
- List,Icons and Split view;
- Move/Copy/Clone/Delete files with Drag & Drop
- Share files or folder to others.
- Add folder to your favorites
- Calculate directory sizes
- Thumbnails for image files
- Normalizer:UTF-8 Normalizer of file-name and file-path etc.
- Muti Charset support, in a variety of circumstances garbled solution;Sanitizer of file-name and file-path etc.
- Multiple & chunked uploads support,
- Background file upload with Drag & Drop HTML5 support;Folder upload with Chrome, Firefox and Edge
- Upload form URL (or list)
- Direct extraction to the current working directory (you do not want - to create a folder)
- Search: search by filename & file contents
- File exclusion based on name
- Copy direct file URL
- Archives create/extract/preview (zip, rar, 7z, tar, gzip, tgz)
- Quicklook, preview for common file types; image file,text file,pdf,swf,document file etc.
- Video and audio player relying on web browser capabilities
- Editor
- Syntax highlighting for over 120 languages
- Multiple label, Drag & Drop the label.
- Over 15 themes,Choose your favorite programming style
- Web development: HTML/JS/CSS editor with Emmet integrated
- Automatic indent and outdent;Line wrapping;Code folding
- Multiple cursors and selections;(Middle key select;Ctrl+Command+G)
- Autocomplete.
- Fully customizable key bindings including vim and Emacs modes
- Search and replace with regular expressions;Highlight matching parentheses
- Toggle between soft tabs and real tabs
- Displays hidden characters
- Drag and drop text using the mouse
- Live syntax checker (JavaScript/CoffeeScript/CSS/XQuery/HTML/PHP etc.)
- Cut, copy, and paste functionality
- Markdown support.(live preview;convert to html etc.)
- Format: JavaScript/CSS/HTML/JSON/PHP etc.
- Cross-platform, even on mobile devices
- Easy to integrate with other systems
- Developed by kod itself, this is a nice try.