> ## Documentation Index > Fetch the complete documentation index at: https://docs.versori.com/llms.txt > Use this file to discover all available pages before exploring further. # projects > Manage projects, deployments, versions, assets, and environments The `projects` command (alias: `project`) provides subcommands for the full project lifecycle — creation, file management, deployment, logging, and more. ## Subcommands | Subcommand | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------ | | `activations` | Manage activations (end-user → environment links). Alias for the activation-lifecycle commands under `versori projects users`. | | `asset` | Manage assets within a project | | `create` | Create a new project in the current organisation | | `deploy` | Deploy the project to versori | | `details` | Get details for a project. Pass in - to read the project id from stdin | | `edit` | Edit project environment configuration (resource limits and requests) | | `environments` | Manage project environments | | `files` | List or read files from a project | | `list` | Lists all projects in the current context | | `logs` | Check the project logs | | `proxy` | Send an HTTP request to a project's deployed environment | | `save` | Save the project files to versori (no deploy) | | `star` | Mark a project as a starred reference project for the organisation | | `sync` | Sync pulls the project files to the local directory. Dry-run by default; pass --confirm to actually write. | | `systems` | Manage systems within a project | | `unstar` | Remove the starred flag from a project | | `users` | Manage users (activations) within a project | | `variables` | Manage a project's DynamicVariablesSchema (declares valid activation-variable keys) | | `versions` | Manage versions within a project. | *** ### `versori projects activations` See the [activations reference](projects/activations) for detailed subcommands to manage activations (end-user → environment links). alias for the activation-lifecycle commands under `versori projects users`. . *** ### `versori projects asset` See the [asset reference](projects/asset) for detailed subcommands to manage assets within a project. *** ### `versori projects create` ```sh theme={null} versori projects create --name [flags] ``` **Flags:** * `-h`, `--help`: help for create * `-n`, `--name`: Name of the project *** ### `versori projects deploy` ```sh theme={null} versori projects deploy [--project ] --environment [--directory ] [flags] ``` **Flags:** * `--assets`: Also upload assets from the versori-research directory * `--description`: Description of the new version. * `-d`, `--directory`: The directory containing the project files * `--dry-run`: Print files that would be uploaded without actually deploying * `--environment`: The project environment to deploy to (e.g. production, staging) * `-h`, `--help`: help for deploy * `--project`: Project ID; defaults from .versori when inside a synced project directory. * `--version`: Name of the version to create (default: current time in UTC, e.g. 2006-01-02-15-04-05) *** ### `versori projects details` ```sh theme={null} versori projects details [flags] ``` **Flags:** * `-h`, `--help`: help for details *** ### `versori projects edit` ```sh theme={null} versori projects edit --project --environment [flags] ``` **Flags:** * `--environment`: The environment name * `-h`, `--help`: help for edit * `--max-replicas`: Maximum number of replicas. Setting this option enables autoscaling on the project * `--project`: Project ID; defaults from .versori when inside a synced project directory. * `--replicas`: Number of replicas * `--resource.cpu.limits`: CPU limits (e.g., 500m) * `--resource.cpu.requests`: CPU requests (e.g., 100m) * `--resource.memory.limits`: Memory limits (e.g., 500Mi) * `--resource.memory.requests`: Memory requests (e.g., 200Mi) * `--resource.storage.limits`: Ephemeral storage limits (e.g., 1Gi) * `--resource.storage.requests`: Ephemeral storage requests (e.g., 1Gi) * `--service-account`: Service account to use for the environment. Pass an empty string to remove the service account * `--static-ip`: Enable or disable static IP (enabled/disabled) *** ### `versori projects environments` See the [environments reference](projects/environments) for detailed subcommands to manage project environments. *** ### `versori projects files` List files in a project, or print a single file's content to stdout. With no arguments, lists files. Default -o table shows filename and size; -o json and -o yaml include file contents too. With a filename, writes that file's content verbatim to stdout so it can be piped to other tools (jq, less, grep, etc.). ```sh theme={null} versori projects files [filename] [flags] ``` **Flags:** * `-h`, `--help`: help for files * `--project`: Project ID; defaults from .versori when inside a synced project directory. * `--version`: Read files from a specific version id instead of the current files *** ### `versori projects list` ```sh theme={null} versori projects list [flags] ``` **Flags:** * `-h`, `--help`: help for list * `--starred`: Only list projects the organisation has starred *** ### `versori projects logs` ```sh theme={null} versori projects logs [flags] ``` **Flags:** * `--environment`: The environment to retrieve logs for. e.g. (production, staging) * `-h`, `--help`: help for logs * `--limit`: How many logs to retrieve; 0 means no explicit limit * `--project`: Project ID; defaults from .versori when inside a synced project directory. * `--search`: Search query to filter logs * `--since`: Go duration since now, e.g. 24h, 2h30m (default: 24h) *** ### `versori projects proxy` Proxy sends an HTTP request to a project's deployed environment and returns the response. This allows triggering a project remotely via an HTTP call. The --body flag accepts a raw string or @filename to read the body from a file. When using @filename, the Content-Type header is automatically inferred from the file extension unless explicitly provided via --header. ```sh theme={null} versori projects proxy --path [flags] ``` **Flags:** * `-b`, `--body`: Request body (string or @filename to read from file) * `-d`, `--data`: HTTP POST data (alias for --body) * `--environment`: Project environment name (e.g. production, staging) * `-H`, `--header`: HTTP headers as key:value pairs (repeatable) * `-h`, `--help`: help for proxy * `-m`, `--method`: HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS) * `--path`: URL path to call on the integration (required) * `--project`: Project ID; defaults from .versori when inside a synced project directory. * `-q`, `--query`: Query parameters as key:value pairs (repeatable) * `-X`, `--request`: HTTP method (alias for --method) * `-u`, `--user`: Server user and password (e.g. user:password) *** ### `versori projects save` ```sh theme={null} versori projects save [--project ] [--directory ] [flags] ``` **Flags:** * `--assets`: Also upload assets from the versori-research directory * `-d`, `--directory`: The directory containing the project files * `--dry-run`: Print files that would be uploaded without actually saving * `-h`, `--help`: help for save * `--project`: Project ID; defaults from .versori when inside a synced project directory. *** ### `versori projects star` ```sh theme={null} versori projects star [flags] ``` **Flags:** * `-h`, `--help`: help for star *** ### `versori projects sync` Sync pulls the project files to the local directory. The --project flag is only required the first time you sync a project. Sync runs in dry-run mode by default and only prints what would be created, updated, or deleted. Pass --confirm to perform the real sync (which overwrites local changes and re-pins .versori). WARNING: When --confirm is set, this will overwrite any local changes and delete any local files that are not part of the remote project. ```sh theme={null} versori projects sync [--project ] [--directory ] ``` **Flags:** * `--assets`: Also sync project assets, removing any that are no longer part of the project from the versori-research directory * `--confirm`: Perform the actual sync. Without this flag, sync only prints what would change (dry-run). * `-d`, `--directory`: The directory to download the project files into * `--dry-run`: Force dry-run (the default when --confirm is omitted). Kept for explicitness; if both --dry-run and --confirm are set, --dry-run wins. * `-h`, `--help`: help for sync * `--project`: Project ID; defaults from .versori when inside a synced project directory. *** ### `versori projects systems` See the [systems reference](projects/systems) for detailed subcommands to manage systems within a project. *** ### `versori projects unstar` ```sh theme={null} versori projects unstar [flags] ``` **Flags:** * `-h`, `--help`: help for unstar *** ### `versori projects users` See the [users reference](projects/users) for detailed subcommands to manage users (activations) within a project. *** ### `versori projects variables` See the [variables reference](projects/variables) for detailed subcommands to manage a project's dynamicvariablesschema (declares valid activation-variable keys) . *** ### `versori projects versions` See the [versions reference](projects/versions) for detailed subcommands to manage versions within a project.. ***