rio-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 rio:
pip install rio-chopt -
Deploy your package :
rio deploy -l path/to/package/foldereg:
rio deploy -l /Users/abcdef@ghi.com/Documents/git/myProjectNote: you will be prompted to enter your docker hub username, password, and email
You can find a sample project here.
- Deploy Package Arguments and Options
rio 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.
rio 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. rio deploy -l /Users/abcdef@ghi.com/Documents/git/myUpdatedProject
or
rio 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 |
|---|---|
| List packages deployed | rio list -l |
| Stop a package ¹ | rio stop -l myProject |
| Stop all packages | rio stop -l --all |
| Start a package | rio start -l myProject |
| Start all packages | rio start -l --all |
| Undeploy a package | rio undeploy -l myProject |
| Undeploy all packages | rio undeploy -l --all |
| Begin RIO session ² ³ | rio begin -l |
| End RIO session | rio 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 RIO Session begins automatically upon running rio deploy or rio list.
³ You can also point to a yaml file like this:
rio 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: rio deploy --help
Metadata
Release files for rio-chopt 1.0.4.2
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 |
|---|---|---|---|---|
| rio-chopt-1.0.4.2.tar.gz | 21.8 kB | Without provenance | Details for rio-chopt-1.0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rio_chopt-1.0.4.2-py3-none-any.whl | Python 3 | none | any | Details for rio_chopt-1.0.4.2-py3-none-any.whl |
Total release size: 51.4 kB
Release files / rio-chopt-1.0.4.2.tar.gz
| Download URL | rio-chopt-1.0.4.2.tar.gz |
|---|---|
| Size | 21.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f50799ebc126b1df37a67526f3e7c8a39a0d7c6a6fb3f59de22c5350a3bc9cd
|
|
BLAKE2b-256 checksum How to use checksums |
3ac5948a896092e7248b98605b3b9395e32253d576baceded7b2993c629eabd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.8.0
|
Release files / rio_chopt-1.0.4.2-py3-none-any.whl
| Download URL | rio_chopt-1.0.4.2-py3-none-any.whl |
|---|---|
| Size | 29.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79c73fe29629c11d3e580a8de5782ed7f7cc4fada9c4ca3c2badb5e412a7e8ba
|
|
BLAKE2b-256 checksum How to use checksums |
a85a207d44670d048375492ed9781a88acf95fd54e7e57c39c156e59c011b866
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.8.0
|
Security for rio-chopt 1.0.4.2
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.