WARNING This documentation is for Cells v2. Looking for Pydio Cells v3 docs?
This section provides definitions for commonly used terms of this documentation.
|Static binary, compiled for each platform.
cells contains all microservices necessary to launch the server platform, as well as a couple of command-line tools to communicate with a running Cells instance.
|Static binary containing
cells and additional microservices for implementing Cells Connect and Cells Enterprise features. Requires a valid license key to run.
|Desktop synchronization client.
cells-sync communicates with a running Cells server.
|Command line client that provides tools to communicate with a running Cells server via its REST API.
|Fully Qualified Domain Name, e.g. files.example.com
|Receives all incoming HTTP/TCP connections to Cells and acts as a load balancer / proxy / routing service to the multiple microservices of the Cells environment.
|Independant brick that exposes a set of internal APIs inside Cells. For example, there are microservices for managing users, workspaces, logs, etc.
|Configuration item describing an entrypoint to the Gateway.
|[ip:port] declared by a Site to bind to a given port of a network interface.
|Users access this URL to connect to Cells. It can be exposed by a third-party Reverse Proxy. It must be fully defined, such as http[s]://<ip|domain>[:port] .
|Cells access to a physical storage, can be seen as a "mount point" to either a local filesystem, a S3-compatible storage, etc. Cells indexes all content detected in all datasources.
|Virtual access to any file/folder indexed in any datasource. Workspaces are managed by Administrators.
|Virtual access granted by users to others on the files they are allowed to see. Cells inherit their parent Workspace security rules, and can be seen as "sandboxed" user-managed workspaces.
|Permissions inheritance system based on roles and groups
|Permissions inheritance system based on Security Policies
|Set of permissions that can be applied to any user.
|Group of users, coming with their own set of permissions. Users can only belong to one group and inherit their parent groups permissions.
|Condition-based rules dynamically computed to filter listings and accesses. Matched against the user/query/metadata context.
|Admin-defined rules for keeping/removing/pruning files versions in each datasource.