Feat: change some word

Signed-off-by: barnettZQG <barnett.zqg@gmail.com>
This commit is contained in:
barnettZQG 2022-04-13 19:11:23 +08:00
parent 19b2e4d7cc
commit 9491a539b5
6 changed files with 26 additions and 30 deletions

View File

@ -2,29 +2,28 @@
title: Project management
---
Projects provide a logical grouping of applications、environments and targets, which is useful when VelaUX is used by multiple teams. Projects provide the following features:
Project provides a logical separation of applications、environments and delivery targets, this is helpful when VelaUX is used by multiple teams. Project can provide the following features:
* restrict where apps may be deployed to (target clusters and namespaces), we plan to support setting resource limits for the target.
* restrict what Integrations can be use(trusted Helm repositories, docker registry or cloud provider)
* defining project roles to provide application RBAC.
* restrict what kinds of objects or component definitions may or may not be deployed(TODO)
* restrict where applications may be deployed to (target clusters and namespaces).
* restrict what integration configs can be use(trusted Helm repositories, docker registries or cloud providers).
* restrict the different permission of each user, provide a multiple-level permission control skill (RBAC).
## The Default Project
Once installed VelaUX has one default project with name `Default`, and owner by admin user. At the same time, the default target and environment are also generated by default and bound in the project.
Once installed VelaUX has one default project with name `Default` owned by the `admin` user. At the same time, the default delivery target and environment are also generated automatically and bound to the project.
## Creating Projects
Users with project management rights can go to `Platform/Projects` pagein this page you could create and delete project.
Users with project management permissions can go to `Platform/Projects` page for settingsin this page you could create and delete project.
![project-list](https://static.kubevela.net/images/1.3/project-list.jpg)
Click the `New Project` button, you can open the drawer page for creating a project. Each project should set a name and owner, the owner user can auto grant the project admin role after the project is created.
Click the `New Project` button for creating a project. Each project should set name and owner, the owner user will be granted the project admin role automatically after the project created.
## Updating Projects
Project owner, alias, and description information support updating. Click the project name and go to the project detail page, you can manage the members and roles in this project.
Project owner, alias, and description fields can be updated. Click the project name and go to the project detail page, you can manage the members and roles in this project.
## Deleting Projects
If there are applications and environments in a project, it can not be deleted. you must delete applications, environments, and targets in the project that you want to delete.
If there are applications and environments living in one project, then deleting the project is not allowed. You must clean up the applications, environments, and targets in the project before you can delete.

View File

@ -2,7 +2,7 @@
title: User management
---
Once installed VelaUX has one built-in `admin` user that has full access to the system. it is recommended to use this user only for initial configuration and then create new user or configure SSO integration.
Once VelaUX is installed, there's a built-in administrator user with full access to the system. It is recommended to use the admin user only for the initial configuration, then switch to another user or configure the SSO integration.
## Local users/accounts
@ -13,7 +13,7 @@ The local users/accounts feature serves two main use-cases:
### Get full users list
If login user have list users permission, he could switch to the `Platform/Users` page and get full users list.
If the logged-in user has the list user permission, he can switch to the `Platforms/Users` page and get the full list of users.
![user list](https://static.kubevela.net/images/1.3/user-dashboard.jpg)

View File

@ -4,10 +4,9 @@ title: 项目管理
项目提供了应用、环境和资源的逻辑分组它适用于多个团队或项目组使用VelaUX的场景他具有以下能力设定
* 限制应用部署的目标,即哪些集群的哪些命名空间,未来我们将支持为交付目标设置资源限额
* 限制应用部署的目标,即哪些集群的哪些命名空间。
* 限制可用的集成配置,包括镜像仓库、制品仓库、云服务授权等。
* 限制不同的用户的管理权限。
* 限制可使用的组件类型和可部署的资源类型(计划中)。
* 限制不同的用户的 RBAC 授权,实现项目和应用多级权限控制。
## 默认项目

View File

@ -4,10 +4,9 @@ title: 项目管理
项目提供了应用、环境和资源的逻辑分组它适用于多个团队或项目组使用VelaUX的场景他具有以下能力设定
* 限制应用部署的目标,即哪些集群的哪些命名空间,未来我们将支持为交付目标设置资源限额
* 限制应用部署的目标,即哪些集群的哪些命名空间。
* 限制可用的集成配置,包括镜像仓库、制品仓库、云服务授权等。
* 限制不同的用户的管理权限。
* 限制可使用的组件类型和可部署的资源类型(计划中)。
* 限制不同的用户的 RBAC 授权,实现项目和应用多级权限控制。
## 默认项目

View File

@ -2,29 +2,28 @@
title: Project management
---
Projects provide a logical grouping of applications、environments and targets, which is useful when VelaUX is used by multiple teams. Projects provide the following features:
Project provides a logical separation of applications、environments and delivery targets, this is helpful when VelaUX is used by multiple teams. Project can provide the following features:
* restrict where apps may be deployed to (target clusters and namespaces), we plan to support setting resource limits for the target.
* restrict what Integrations can be use(trusted Helm repositories, docker registry or cloud provider)
* defining project roles to provide application RBAC.
* restrict what kinds of objects or component definitions may or may not be deployed(TODO)
* restrict where applications may be deployed to (target clusters and namespaces).
* restrict what integration configs can be use(trusted Helm repositories, docker registries or cloud providers).
* restrict the different permission of each user, provide a multiple-level permission control skill (RBAC).
## The Default Project
Once installed VelaUX has one default project with name `Default`, and owner by admin user. At the same time, the default target and environment are also generated by default and bound in the project.
Once installed VelaUX has one default project with name `Default` owned by the `admin` user. At the same time, the default delivery target and environment are also generated automatically and bound to the project.
## Creating Projects
Users with project management rights can go to `Platform/Projects` pagein this page you could create and delete project.
Users with project management permissions can go to `Platform/Projects` page for settingsin this page you could create and delete project.
![project-list](https://static.kubevela.net/images/1.3/project-list.jpg)
Click the `New Project` button, you can open the drawer page for creating a project. Each project should set a name and owner, the owner user can auto grant the project admin role after the project is created.
Click the `New Project` button for creating a project. Each project should set name and owner, the owner user will be granted the project admin role automatically after the project created.
## Updating Projects
Project owner, alias, and description information support updating. Click the project name and go to the project detail page, you can manage the members and roles in this project.
Project owner, alias, and description fields can be updated. Click the project name and go to the project detail page, you can manage the members and roles in this project.
## Deleting Projects
If there are applications and environments in a project, it can not be deleted. you must delete applications, environments, and targets in the project that you want to delete.
If there are applications and environments living in one project, then deleting the project is not allowed. You must clean up the applications, environments, and targets in the project before you can delete.

View File

@ -2,7 +2,7 @@
title: User management
---
Once installed VelaUX has one built-in `admin` user that has full access to the system. it is recommended to use this user only for initial configuration and then create new user or configure SSO integration.
Once VelaUX is installed, there's a built-in administrator user with full access to the system. It is recommended to use the admin user only for the initial configuration, then switch to another user or configure the SSO integration.
## Local users/accounts
@ -13,7 +13,7 @@ The local users/accounts feature serves two main use-cases:
### Get full users list
If login user have list users permission, he could switch to the `Platform/Users` page and get full users list.
If the logged-in user has the list user permission, he can switch to the `Platforms/Users` page and get the full list of users.
![user list](https://static.kubevela.net/images/1.3/user-dashboard.jpg)