Skip to main content

Riker

You’re the captain, and Riker is your “Number One”

Heroku-like application deployments to Amazon Web Services.

Install

pip install riker

Configure

riker config

Usage

Deploy a sample app to AWS with a single command:

# Get Python sample app
git clone git@github.com:heroku/python-sample.git
cd python-sample

riker deploy
riker open

This will launch an EC2 instance running the python-sample app, and open it in your default web browser.

The first time this is run in your AWS account, it will take some time, as it needs to provision a base AMI which all EC2 instances will be launched from. Subsequent deploys to the same app will be very quick, and new application deployments will only need to wait for a new EC2 instance to boot.

Since Riker uses Heroku Buildpacks, the app can be written in any language.

You can also deploy a static website to S3 with the same command:

# Generate simple website
mkdir static-website && cd static-website
echo "Hello, World" > index.html
touch .s3 # indicates deployment to Amazon S3
git init && git add -A && git commit -m "Initial commit"

riker deploy
riker open

The .s3 file indicates that this app should be deployed to S3.

Riker also supports a production deploy mode, which ensures zero-downtime for the application being deployed, and a configuration which supports auto-scaling. Usually, Riker will deploy changes directly to existing instances. However, for a production deployment, Riker will deploy changes to new instances, and only swap old instances out for new instances when the new instances become healthy, and the old instances no longer have active connections.

riker deploy --scale

This will deploy the app behind a load-balancer and auto-scaling group.

Contributing

Please report bugs, suggest features, and ask questions on GitHub: https://github.com/jschementi/riker/issues

Pull requests welcome! https://github.com/jschementi/riker/pulls

Additional Resources

Metadata

Release files for riker 0.2.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for riker 0.2.4
File Size Uploaded Provenance Actions
riker-0.2.4.tar.gz 26.3 kB Without provenance Details for riker-0.2.4.tar.gz

Release files / riker-0.2.4.tar.gz

Download URL riker-0.2.4.tar.gz
Size 26.3 kB
Tags Source
SHA-256 checksum
How to use checksums
1c9d09e34dfe32368654702ae3935c69271ff0256ccf7a89e24a2c5c5182ac31
BLAKE2b-256 checksum
How to use checksums
69d6417a3bb70253daa7d7dca5916c11c626aca3c5a10d07a50663c7f9545747
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for riker 0.2.4

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page