roe-cli
This utility helps you deploy your code as an API locally on your machine using Docker. It is a python based package that can be installed via pip.
Quickstart
-
Install roe:
pip install roe -
Deploy your package :
roe deploy -l path/to/package/foldereg:
roe deploy -l /Users/abcdef@ghi.com/Documents/git/myProjectNote: you will be prompted to enter your docker hub username and password
You can find a sample project here.
- Deploy Package Arguments and Options
roe deploy -l path/to/package/folder
-lis for local deployment (only local is available for now).-nis for specifying a package name. If left out, the folder name is chosen as package name.-pis a port you specify for it to be spun up on(The valid range is 1024-65535). If left out, a port will be assigned.-qis to deploy with no extra prompts to affirm redeployments and no webpage opening when finishing the deployment.
- Re-deploying a package.
roe deploy -l path/to/package/folder
If you used a custom name for your package, you will have to specify it with the package name (-n) flag just like you did initially.
e.g. roe deploy -l /Users/abcdef@ghi.com/Documents/git/myUpdatedProject
or
roe deploy -l -n myCustomName /Users/abcdef@ghi.com/Documents/git/myUpdatedProject
Note: It will re-use the port from the first deployment.
Other commands:
| Description | Command |
|---|---|
| Verify package configuration | roe verify -l path/to/package/folder |
| List packages deployed | roe list -l |
| Stop a package ¹ | roe stop -l -p myProject |
| Stop all packages | roe stop -l --all |
| Start a package | roe start -l myProject |
| Start all packages | roe start -l --all |
| Undeploy a package | roe undeploy -l -p myProject |
| Undeploy all packages | roe undeploy -l --all |
| Begin ROE session ² ³ | roe begin -l |
| End ROE session | roe end -l |
¹ If a model API associated with this package is running, you will be asked to enter 'Y' to stop it and proceed with deleting the package.
² A ROE Session begins automatically upon running roe deploy or roe list.
³ You can also point to a yaml file like this:
roe begin -l -f /Users/myUser/Documents/docker-creds.yaml. Download a sample credential
file here.
You can use the --help command in front of any command from within the CLI for help with options and arguments.
Eg: roe deploy --help
Metadata
Release files for roe 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| roe-1.0.3.tar.gz | 23.8 kB | Without provenance | Details for roe-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| roe-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for roe-1.0.3-py3-none-any.whl |
Total release size: 58.0 kB
Release files / roe-1.0.3.tar.gz
| Download URL | roe-1.0.3.tar.gz |
|---|---|
| Size | 23.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1d35915b7628818446d900fc6c1ce96628ffe6559d9ed335691c60aff5fa207
|
|
BLAKE2b-256 checksum How to use checksums |
4f7166075f0f0e09d28c6230ab26b8a43c19e1c4f409ac8b7b7a84ae830ba65f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
|
Release files / roe-1.0.3-py3-none-any.whl
| Download URL | roe-1.0.3-py3-none-any.whl |
|---|---|
| Size | 34.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0e12d176824ac86f9e63960b703055233b75aaf4a55bc13f00c1c08b2a87947
|
|
BLAKE2b-256 checksum How to use checksums |
54bf0d5a7b39ff430c598db77ee0af0a71d5ed82ee9539e688c55ba6e3c35f8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
|
Security for roe 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.