This is not-even-alpha quality software. I'm implementing parts of the API on an as-needed basis for my own use. Pull Requests and formal adoption by the render.com team are more than welcome and will be responded to fairly quickly.
These are the only two commands currently:
render put-env <service_name> <env_fpath...>
render deploy <service_name>
It authorizes your requests by looking for RENDER_TOKEN
in your environment.
Generate a token on the Render.com web interface, and then add it to your environment.
You can add it to your environment like below.
I recommend against adding secrets to ~/.bash_profile
, so it's stored in ~/.renderrc
.
# ~/.renderrc
export RENDER_TOKEN=<your token>
# ~/.bash_profile
source ~/.renderrc
The rest of the documentation is available from --help
:
render-cli 0.1.0
Kurt Wolf <kurtwolfbuilds@gmail.com>
Command line actions for Render.com
USAGE:
render [OPTIONS] <SUBCOMMAND>
OPTIONS:
-h, --help Print help information
--token <TOKEN> The API key. Can be set with env var RENDER_TOKEN
-V, --version Print version information
SUBCOMMANDS:
deploy
help Print this message or the help of the given subcommand(s)
put-env Update the service environment variables
cargo install render-cli
Alternatively, install from source:
git clone https://github.com/kurtbuilds/render
cd render
just install
There isn't one! Here's where the project is at:
Bug reports are extremely welcome, as are pull requests for new features. Feature requests will mostly be ignored, because, again, I built this for my own use.
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
git checkout -b feature/AmazingFeature
)git commit -m 'Add some AmazingFeature'
)git push origin feature/AmazingFeature
)