0
Fork 0
mirror of https://github.com/verdaccio/verdaccio.git synced 2024-12-16 21:56:25 -05:00

New Crowdin translations (#778)

* New translations ansible.md (Chinese Simplified)
docs(website): new translations

* New translations auth.md (Chinese Simplified)
docs(website): new translations

* New translations build.md (Chinese Simplified)
docs(website): new translations

* New translations contributing.md (Chinese Simplified)
docs(website): new translations

* New translations ci.md (Chinese Simplified)
docs(website): new translations

* New translations chef.md (Chinese Simplified)
docs(website): new translations

* New translations contributing.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations ansible.md (Chinese Simplified)
docs(website): new translations

* New translations ci.md (Chinese Simplified)
docs(website): new translations

* New translations plugins.md (Spanish)
docs(website): new translations

* New translations notifications.md (Spanish)
docs(website): new translations

* New translations auth.md (Chinese Simplified)
docs(website): new translations

* New translations contributing.md (Chinese Simplified)
docs(website): new translations

* New translations build.md (Chinese Simplified)
docs(website): new translations

* New translations chef.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations packages.md (Chinese Simplified)
docs(website): new translations

* New translations plugins.md (Chinese Simplified)
docs(website): new translations

* New translations plugins.md (Chinese Simplified)
docs(website): new translations

* New translations plugins.md (Chinese Simplified)
docs(website): new translations
This commit is contained in:
verdacciobot 2018-06-23 16:42:14 +02:00 committed by Juan Picado @jotadeveloper
parent dcd5d9a7c7
commit 18c0b5458a
4 changed files with 70 additions and 70 deletions

View file

@ -64,7 +64,7 @@ Lista de las propiedades accesibles mediante el modelo
### Metadata
Empaqueta la metadata a la que el modelo tiene acceso
Paquete de metadata a la que el modelo tiene acceso
{
"_id": "@test/pkg1",
@ -117,9 +117,9 @@ Empaqueta la metadata a la que el modelo tiene acceso
### Publisher
Puede accesar a la información del paquete publisher en el `content` de una webhook usando el objeto `publisher`.
Puede acceder a la información del paquete publisher en el `content` de una webhook usando el objeto `publisher`.
Vea debalo del tipo de objeto `publisher`:
Vea a continuación el tipo de objeto `publisher`:
{
name: string,
@ -137,11 +137,11 @@ Un ejemplo:
content: '{"color":"green","message":"New package published: * {{ name }}*. Publisher name: * {{ publisher.name }} *.","notify":true,"message_format":"text"}'
**Nota:** no es posible obtener la informacion de publisher si el archivo `package.json` ya tiene la propiedad `publisher`.
**Nota:** no es posible obtener la información de publisher si el archivo `package.json` ya tiene la propiedad `publisher`.
### Paquete Publicado
Puede accesar al paquete que está siendo publicado con el comando `{{publishedPackage}}` como a continuación.
Puede acceder al paquete que está siendo publicado con el comando `{{publishedPackage}}` como a continuación.
{{ publisher.name }} has published {{publishedPackage}}"}

View file

@ -1,8 +1,8 @@
---
id: plugins
title: "Complementos"
title: "Plugins"
---
Verdaccion es una aplicación extensible. Puede ser extendida en muchas maneras, tanto con nuevos métodos de autenticación, añadiendo endpoints o usando un almacenamiento personalizado.
Verdaccio es una aplicación extensible. Puede ser extendida en muchas maneras, tanto con nuevos métodos de autenticación, añadiendo endpoints o usando un almacenamiento personalizado.
> Si está interesado en desarrollar su propio plugin, lea la sección [development](development.md).
@ -14,7 +14,7 @@ Verdaccion es una aplicación extensible. Puede ser extendida en muchas maneras,
$> npm install --global verdaccio-activedirectory
```
`verdaccion` como un fork de sinopia tiene compatibilidad con versiones anteriores, con plugins que son compatibles con `sinopia@1.4.0`. En tal caso la instalación es la misma.
`verdaccio` como un fork de sinopia tiene compatibilidad con versiones anteriores, con plugins que son compatibles con `sinopia@1.4.0`. En tal caso la instalación es la misma.
$> npm install --global sinopia-memory
@ -68,7 +68,7 @@ middlewares:
enabled: true
```
### Configuraión del Plugin Store (Almacén)
### Configuración del Plugin Store (Almacén)
Este es un ejemplo de como instalar un plugin de almacenamiento. Todos los plugins de almacenamiento debe estar definidos en el namespace **store**.
@ -78,7 +78,7 @@ store:
limit: 1000
```
> Si define un almacén personalizado, la propiedad **storage** en el archivo de configuración será ignorada.
> Si define un almacenamiento personalizado, la propiedad **storage** en el archivo de configuración será ignorada.
## Plugins heredados
@ -89,14 +89,14 @@ store:
* [sinopia-npm](https://www.npmjs.com/package/sinopia-npm): plugin auth para sinopia soportando un registro npm.
* [sinopia-memory](https://www.npmjs.com/package/sinopia-memory): plugin auth para sinopia que mantiene a los usuarios en la memoria.
* [sinopia-github-oauth-cli](https://www.npmjs.com/package/sinopia-github-oauth-cli).
* [sinopia-crowd](https://www.npmjs.com/package/sinopia-crowd): plugin auth para sinopia que soporta la multitud de atlassian.
* [sinopia-crowd](https://www.npmjs.com/package/sinopia-crowd): plugin auth para sinopia que soporta atlassian crowd.
* [sinopia-activedirectory](https://www.npmjs.com/package/sinopia-activedirectory): plugin de autenticación Active Directory para sinopia.
* [sinopia-github-oauth](https://www.npmjs.com/package/sinopia-github-oauth): plugin de autenticación para sinopia2, el cual soporta el flujo web de github oauth.
* [sinopia-delegated-auth](https://www.npmjs.com/package/sinopia-delegated-auth): plugin de autenticación de Sinopia que delega autenticación a otro URL HTTP
* [sinopia-altldap](https://www.npmjs.com/package/sinopia-altldap): Alterna el plugin LDAP Auth para Sinopia
* [sinopia-request](https://www.npmjs.com/package/sinopia-request): Un complemento sencillo y completamente auth con configuración para usar una API externa.
* [sinopia-htaccess-gpg-email](https://www.npmjs.com/package/sinopia-htaccess-gpg-email): Genera contraseña en formato htaccess, encripta con GPG y evía a través de la API MailGun a los usuarios.
* [sinopia-mongodb](https://www.npmjs.com/package/sinopia-mongodb): Un complemento fácil y completamente auth con configuración para usar una base de datos mongodb.
* [sinopia-request](https://www.npmjs.com/package/sinopia-request): Un plugin sencillo y completamente auth con configuración para usar una API externa.
* [sinopia-htaccess-gpg-email](https://www.npmjs.com/package/sinopia-htaccess-gpg-email): Genera contraseña en formato htaccess, encripta con GPG y la evía a través de la API MailGun a los usuarios.
* [sinopia-mongodb](https://www.npmjs.com/package/sinopia-mongodb): Un plugin fácil y completamente auth con configuración para usar una base de datos mongodb.
* [sinopia-htpasswd](https://www.npmjs.com/package/sinopia-htpasswd): plugin auth para sinopia que soporta el formato htpasswd.
* [sinopia-leveldb](https://www.npmjs.com/package/sinopia-leveldb): un plugin auth leveldb respaldado para el npm privado de sinopia.
* [sinopia-gitlabheres](https://www.npmjs.com/package/sinopia-gitlabheres): plugin de autenticación de Gitlab para sinopia.
@ -116,7 +116,7 @@ store:
* [verdaccio-ldap](https://www.npmjs.com/package/verdaccio-ldap): plugin LDAP auth para verdaccio.
* [verdaccio-active-directory](https://github.com/nowhammies/verdaccio-activedirectory): plugin de autenticación Active Directory para verdaccio
* [verdaccio-gitlab](https://github.com/bufferoverflow/verdaccio-gitlab): use la Token de Acceso Personal de GitLab para autenticarse
* [verdaccio-htpasswd](https://github.com/verdaccio/verdaccio-htpasswd): basado en Auth en el plugin del archivo htpasswd (incorporado) para verdaccio
* [verdaccio-htpasswd](https://github.com/verdaccio/verdaccio-htpasswd): Auth basado en el plugin del archivo htpasswd (incorporado) para verdaccio
### Plugins de Middleware

View file

@ -1,14 +1,14 @@
---
id: packages
title: "Package Access"
title: "包的访问"
---
It's a series of contraints that allow or restrict access to the local storage based in specific criteria.
这是一系列的约束,它基于特定条件允许或限制对本地存储的访问。
The security constraints remain on the shoulders of the plugin being used, by default `verdaccio` uses the [htpasswd plugin](https://github.com/verdaccio/verdaccio-htpasswd). If you use a different plugin the behaviour might be different. The default plugin does not handle `allow_access` and `allow_publish` by itself, it uses an internal fallback in case the plugin is not ready for it.
安全约束构建于被使用的插件上,在默认情况下,`verdaccio`使用[htpasswd plugin](https://github.com/verdaccio/verdaccio-htpasswd)。 如果你使用不同的插件,行为可能会有所不同。 默认插件自己并不处理`allow_access`和`allow_publish`,它使用内部回退功能以防止插件尚未就绪。
For more information about permissions visit [the authentification section in the wiki](auth.md).
关于权限的更多信息,请访问[维基文档的认证部分](auth.md)。
### Usage
### 用法
```yalm
packages:
@ -31,7 +31,7 @@ packages:
proxy: uplink2
```
if none is specified, the default one remains
如果未进行任何设置,默认值则会被保留
```yaml
packages:
@ -40,20 +40,20 @@ packages:
publish: $authenticated
```
The list of valid groups according the default plugins are
根据默认插件设置,有效的组列表为
```js
'$all', '$anonymous', '@all', '@anonymous', 'all', 'undefined', 'anonymous'
```
All users recieve all those set of permissions independently of is anonymous or not plus the groups provided by the plugin, in case of `htpasswd` return the username as a group. For instance, if you are logged as `npmUser` the list of groups will be.
All users recieve all those set of permissions independently of is anonymous or not plus the groups provided by the plugin, in case of `htpasswd` return the username as a group. 例如,如果你以`npmUser`身份登录,组列表为:
```js
// groups without '$' are going to be deprecated eventually
'$all', '$anonymous', '@all', '@anonymous', 'all', 'undefined', 'anonymous', 'npmUser'
```
If you want to protect specific set packages under your group, you need to do something like this. Let's use a `Regex` that covers all prefixed `npmuser-` packages. We recomend using a prefix for your packages, in that way it will be easier to protect them.
如果你想要保护你所在组的特定包,你需要做如下工作。 我们来使用一个包含所有前缀为`npmuser-`的包的`Regex`。 我们建议在包前使用前缀,通过这种方式更容易保护它们。
```yaml
packages:
@ -62,7 +62,7 @@ packages:
publish: npmuser
```
Restart `verdaccio` and in your console try to install `npmuser-core`.
重启`verdaccio`并在命令行中安装`npmuser-core`。
```bash
$ npm install npmuser-core
@ -74,11 +74,11 @@ npm ERR! A complete log of this run can be found in:
npm ERR! /Users/user/.npm/_logs/2017-07-02T12_20_14_834Z-debug.log
```
You can change the existing behaviour using a different plugin authentication. `verdaccio` just checks whether the user that tried to access or publish a specific package belongs to the right group.
你可以使用不同的插件认证来更改现有行为。 `verdaccio`只是检查试图访问或发布特定包的用户是否属于正确的组。
#### Set multiple groups
#### 设置多个组
Defining multiple access groups is fairly easy, just define them with a white space between them.
定义多个访问组非常简单,只需要在它们之间加入一个空格。
```yaml
'company-*':
@ -92,9 +92,9 @@ Defining multiple access groups is fairly easy, just define them with a white sp
```
#### Blocking access to set of packages
#### 阻止对一组包的访问
If you want to block the acccess/publish to a specific group of packages. Just do not define `access` and `publish`.
如果你想要阻止访问/发布到一组包,只需要避免定义`access` 和 `publish`
```yaml
packages:
@ -104,11 +104,11 @@ packages:
publish: $authenticated
```
#### Blocking proxying a set of specific packages
#### 阻止代理一组特定包
You might want to block one or several packages from fetching from remote repositories., but, at the same time, allow others to access different *uplinks*.
你可能想要阻止一个或多个包从远程库获取数据,但在同时,允许其他包访问不同的*uplinks*。
Let's see the following example:
请看如下示例:
```yaml
packages:
@ -127,24 +127,24 @@ packages:
proxy: npmjs
```
Let's describe what we want with the above example:
让我们描述一下在上面的示例中我们想要做什么:
* I want to host my own `jquery` dependency but I need to avoid proxying it.
* I want all dependencies that match with `my-company-*` but I need to avoid proxying them.
* I want all dependencies that are in the `my-local-scope` scope but I need to avoid proxying them.
* I want proxying for all the rest of the dependencies.
* 我想要自己的服务器上放置`jquery`依赖库但需要避免代理它。
* 我想要所有和`my-company-*`匹配的依赖库但我需要避免代理它们。
* 我想要在`my-local-scope`范围内的所有依赖库但我需要避免代理它们。
* 我想要代理所有剩余的依赖库。
Be **aware that the order of your packages definitions is important and always use double wilcard**. Because if you do not include it `verdaccio` will include it for you and the way that your dependencies are resolved will be affected.
**注意库定义的顺序很重要同时必须使用配对的通配符**。 因为如果你没有包含它,`verdaccio`会帮你来包含它,这样你的依赖库解析会受到影响。
### Configuration
### 配置
You can define mutiple `packages` and each of them must have an unique `Regex`.
你可以定义多个`包`,每个包都必须有一个唯一的`Regex`。
| Property | Type | Required | Example | Support | Description |
| -------- | ------- | -------- | -------------- | ------- | ------------------------------------------- |
| access | string | No | $all | all | define groups allowed to access the package |
| publish | string | No | $authenticated | all | define groups allowed to publish |
| proxy | string | No | npmjs | all | limit look ups for specific uplink |
| storage | boolean | No | [true,false] | all | TODO |
| 属性 | 类型 | 必须的 | 范例 | 支持 | 描述 |
| ------- | ------- | --- | -------------- | --- | --------------- |
| access | string | No | $all | all | 定义允许访问包的组 |
| publish | string | No | $authenticated | all | 定义允许发布的组 |
| proxy | string | No | npmjs | all | 针对特定的uplink限制查找 |
| storage | boolean | No | [true,false] | all | TODO |
> We higlight that we recommend to not use **allow_access**/**allow_publish** and **proxy_access** anymore, those are deprecated and will soon be removed, please use the short version of each of those (**access**/**publish**/**proxy**).
> 我们强烈建议不要再使用已被弃用的**allow_access**/**allow_publish** 和 **proxy_access**,它们很快就会被移除,请使用它们的精简版本 (**access**/**publish**/**proxy**) 。

View file

@ -1,31 +1,31 @@
---
id: plugins
title: "Plugins"
title: "插件"
---
Verdaccio is an plugabble aplication. It can be extended in many ways, either new authentication methods, adding endpoints or using a custom storage.
Verdaccio是一个可插拔的应用程序。它可以通过多种方式进行扩展例如新的认证方法添加endpoints或者使用自定义存储。
> If you are interested to develop your own plugin, read the [development](development.md) section.
> 如果你对开发自己的插件感兴趣,请阅读[开发](development.md)部分。
## Usage
## 用法
### Installation
### 安装
```bash
$> npm install --global verdaccio-activedirectory
```
`verdaccio` as a sinopia fork it has backward compability with plugins that are compatible with `sinopia@1.4.0`. In such case the installation is the same.
`verdaccio`作为一个sinopia的分支它和兼容`sinopia@1.4.0`的插件具有向后兼容性。在这种情况下,安装方式相同。
$> npm install --global sinopia-memory
### Configuration
### 配置
Open the `config.yaml` file and update the `auth` section as follows:
打开`config.yaml`文件并按如下说明更新`auth`部分:
The default configuration looks like this, due we use a build-in `htpasswd` plugin by default that you can disable just commenting out the following lines.
默认配置如下所示,由于在默认情况下我们使用一个内置的`htpasswd`插件,我们可以通过注释下面几行代码来禁用它:
### Auth Plugin Configuration
### Auth插件配置
```yaml
htpasswd:
@ -33,7 +33,7 @@ The default configuration looks like this, due we use a build-in `htpasswd` plug
#max_users: 1000
```
and replacing them with (in case you decide to use a `ldap` plugin.
如果你决定使用`ldap`插件,将上述部分进行替换。
```yaml
auth:
@ -43,9 +43,9 @@ auth:
domainSuffix: 'sample.local'
```
#### Multiple Auth plugins
#### 多个授权插件
This is tecnically possible, the plugins order becames important, the the credentials will resolved in order.
这在技术上可行,插件的顺序变得非常重要,安全凭据将按顺序获取。
```yaml
auth:
@ -58,9 +58,9 @@ auth:
domainSuffix: 'sample.local'
```
### Middleware Plugin Configuration
### 中间件插件配置
This is an example how to set up a middleware plugin. All middleware plugins must be defined in the **middlewares** namespace.
这是一个如何设置中间件插件的示例。所有的中间件插件必须被定义在**middlewares**命名空间。
```yaml
middlewares:
@ -68,9 +68,9 @@ middlewares:
enabled: true
```
### Store Plugin Configuration
### 存储插件配置
This is an example how to set up a storage plugin. All storage plugins must be defined in the **store** namespace.
这是一个如何设置存储插件的示例。所有的存储插件必须在**store**命名空间进行定义。
```yaml
store:
@ -78,15 +78,15 @@ store:
limit: 1000
```
> If you define a custom store, the property **storage** in the configuration file will be ignored.
> 如果你定义一个自定义存储,配置文件中的**storage**属性将会被忽略。
## Legacy plugins
## 旧式插件
### Sinopia Plugins
### Sinopia插件
(compatible all versions)
(兼容所有版本)
* [sinopia-npm](https://www.npmjs.com/package/sinopia-npm): auth plugin for sinopia supporting an npm registry.
* [sinopia-npm](https://www.npmjs.com/package/sinopia-npm)支持npm注册表的sinopia认证插件。
* [sinopia-memory](https://www.npmjs.com/package/sinopia-memory): auth plugin for sinopia that keeps users in memory.
* [sinopia-github-oauth-cli](https://www.npmjs.com/package/sinopia-github-oauth-cli).
* [sinopia-crowd](https://www.npmjs.com/package/sinopia-crowd): auth plugin for sinopia supporting atlassian crowd.