This release is a pre-release and may not be stable for production use.
reflex-hosting-cli
Hosting CLI for Reflex.
When an app is still scaling, reflex deploy waits 15 seconds between confirmed
scaling refusals, for up to 7 retries to update instance bounds and 11 retries
to submit the deployment. The CLI reports each wait, and you can cancel
with Ctrl-C. Submission retries reuse the uploaded build. The SDK's usual safe
retries can add two more submission attempts, for up to 14 attempts in total;
they do not restart the scaling wait budget. The scaling sleeps total at most
165 seconds for submission; requests and SDK backoff add to elapsed time.
Other failures, including a lost submission response, are reported without
replaying an uncertain write.
If an instance-bounds write has an uncertain outcome, including a server error,
the CLI warns that the bounds may have changed.
A success response that cannot be decoded also stops deployment with a separate
warning about bounds left changed.
If an access token is expired or rejected, run reflex login to authenticate
again. If you supply a token explicitly, replace it with a valid token or remove
the override before using the saved login: unset REFLEX_ACCESS_TOKEN or omit
--token. Logging in does not replace an environment variable or command-line
token. Noninteractive commands exit on rejection without opening a browser.
Metadata
Release files for reflex-hosting-cli 0.2.1a1
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 | |
|---|---|---|---|---|
| reflex_hosting_cli-0.2.1a1.tar.gz | 84.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reflex_hosting_cli-0.2.1a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 178.0 kB
Release files / reflex_hosting_cli-0.2.1a1.tar.gz
| Download URL | reflex_hosting_cli-0.2.1a1.tar.gz |
|---|---|
| Size | 84.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5628a87537a67cd0068bc1f0701f2e9de6bc287a50186dabfcef9d03946cbece
|
|
BLAKE2b-256 checksum How to use checksums |
b63a754a191a176a477a090087e06e3ec713861093b5dc0e83d239d152d8bad9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / reflex_hosting_cli-0.2.1a1-py3-none-any.whl
| Download URL | reflex_hosting_cli-0.2.1a1-py3-none-any.whl |
|---|---|
| Size | 93.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a94dfed7cb2a9bee1b8ba4a072f136269fbb5786e541240ad4390cb64a1f6df2
|
|
BLAKE2b-256 checksum How to use checksums |
d4a8f61b0891b6eb91d4a51e035eef0092c91db3e4d488bf3483bcfb7a088bc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for reflex-hosting-cli 0.2.1a1
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.
