rx is a command-line tool that makes it easy to create, use, and share development environments. It integrates with whatever tools you're currently using and gives you a long-running VM in the cloud that is kept in sync with your local machine.
Usage
In the directory containing your project (often your git root), run:
rx init
This will prompt you to log in (or create an account) and allocate a machine in the cloud for you to use. Then it will copy your project from your local machine to the cloud instance and install any packages that your project needs.
It may take several minutes to allocate a machine, copy your source code, and install packages (depending on your project).
Once rx finishes initializing, you can run any command on your remote worker by prefixing it with "rx":
rx python my-script.py
rx ps ax
rx 'echo $PATH > my-path.txt'
Check out the getting-started section for more examples.
What rx does
When you run rx it takes care of a bunch of cloud setup tasks on your behalf:
- It creates a private hosted environment for your project in the cloud.
- It copies your source code into that environment.
- It installs any dependencies your project needs.
Then, every time you run a command, it automatically syncs local changes to your cloud instance and syncs outputs back to your local machine. rx hosts your environment on our own cloud instances, so you never have to worry about setup or teardown.
Check out the getting started guide to start using rx in less than five minutes.
Note: the rx binary is a thin client and does not run commands on your local
machine: it sends them to your cloud instance and runs them there.
We'd love to hear what you think of rx and how you're using it! Please let us know by emailing eng@run-rx.com or filing an issue on GitHub!
Feedback
Feel free to file an issue if you have any questions or problems.
Running tests
Run tests with:
pip install -r requirements_dev.txt
python run_tests.py
Metadata
Release files for run-rx 0.1.0
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 |
|---|---|---|---|---|
| run_rx-0.1.0.tar.gz | 47.0 kB | Without provenance | Details for run_rx-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| run_rx-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for run_rx-0.1.0-py3-none-any.whl |
Total release size: 112.7 kB
Release files / run_rx-0.1.0.tar.gz
| Download URL | run_rx-0.1.0.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d10b0351d7b9ddd2eae0eb2aa23936248c34f09c15e2860dd3bd5585ed97771
|
|
BLAKE2b-256 checksum How to use checksums |
5c417a2bcabb68bf9b25b726eb3566983ed3d383d96c2d80a7cb7a69dd3328bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.2
|
Release files / run_rx-0.1.0-py3-none-any.whl
| Download URL | run_rx-0.1.0-py3-none-any.whl |
|---|---|
| Size | 65.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d809e24864924b545f06c716a3c354f52a49afe8f3ee1ff9fa246d834022b51f
|
|
BLAKE2b-256 checksum How to use checksums |
c48f56e3a1b7562371afe419e05a4a2be8e71df25a7270415646f6dd0dd26826
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.2
|
Security for run-rx 0.1.0
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.