Redis®*: 3. Pick the instance size

This documentation is part of the GitHub Actions & GitLab CI guide. View the full guide here: Spin up a real Redis service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically.

👋 Welcome to the Stackhero documentation!

Stackhero offers a ready-to-use Redis cloud solution that provides a host of benefits, including:

  • Redis Commander web UI included.
  • Unlimited message size and transfers.
  • Effortless updates with just a click.
  • Optimal performance and robust security powered by a private, dedicated infrastructure.

Save time and simplify your life: it only takes 5 minutes to try Stackhero's Redis cloud hosting solution!

The examples below use the entry-level instance 1G for Redis by default. This is a solid choice for most workloads, but you are welcome to adjust it as needed. To view all available instance types for Redis, you can run:

# The NAME column shows the value to pass to --instance
stackhero instances-store-list --service-store=redis

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Spin up a real Redis service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically
  2. 1. Create an access token and store it as a CI secret
  3. 2. The lifecycle script
  4. 4. GitHub Actions
  5. 5. GitLab CI

Other articles for Redis®*

  1. Getting started
    Quick guide to getting started with Redis
  2. Prometheus
    Prometheus metrics
  3. Using with Python
    How to connect Redis with Python
  4. Using with Ruby
    How to connect Redis with Ruby
  5. Automate with the CLI
    Start Redis, retrieve its credentials, and change its configuration programmatically with the Stackhero CLI
  6. Rank users in real time
    Learn how to rank 2 million users per score in real time using Redis