Memcached: 3. Choose the instance size

This documentation is part of the GitHub Actions & GitLab CI guide. You can view the complete guide here: Launch a real Memcached service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down.

Welcome to the Stackhero documentation

Stackhero offers a fully managed Memcached cloud that simplifies application caching while ensuring security and high performance.

  • Apply updates in just seconds with a single click.
  • Enjoy consistent performance and enhanced security on a private, dedicated infrastructure.

Save time and focus on development. Stackhero's Memcached cloud hosting is up and running in about 5 minutes.

The examples below use the entry-level instance 1G for Memcached by default. This is a reliable choice for most workloads, but you can adjust it as needed. To see all available instance types for Memcached, run:

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

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Launch a real Memcached service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down
  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 Memcached

  1. Getting Started
    How to get started with Memcached
  2. Automate with the CLI
    Start Memcached, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI