API Reference
lean cloud push
Description
Pushes local projects to QuantConnect while preserving the directory structure of your local projects.
The project's supported files, description, and parameters are pushed to the cloud.
By default, all local projects in your current organization workspace directory are pushed. If you provide a --project option, you only push a single project to the cloud.
Before pushing a local project, the CLI checks if the cloud project with the same path already exists.
If it does and the cloud project is not linked to the local project (because of an earlier lean cloud pull or lean cloud push), the CLI adds a 1 to the end of the name of your local project and then pushes it to the cloud.
If the cloud project doesn't exist yet, the CLI creates it for you and pushes the contents of the local project to the newly created cloud project.
If you have a cloud copy of a project when you push it from your local machine, files in the cloud which don't exist locally are deleted and the configuration values of your local project overwrite the configuration values of the cloud version. If you have renamed the project on your local machine or in the cloud before you push, the cloud project is renamed to match the name of the local project.
Options
The lean cloud push command supports the following options:
| Option | Description |
|---|---|
--project <directory> | Path to the local project to push (all local projects if not specified) |
--encrypt | Push your local files and encrypt them before saving on the cloud |
--decrypt | Push your local files and decrypt them before saving on the cloud |
--key <file> | Path to the encryption key to use |
--verbose | Enable debug logging |
--help | Display the help text of the lean cloud push command and exit |
You can also see our Videos. You can also get in touch with us via Discord.
Did you find this page helpful?
