Memcached: 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 Memcached 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 provides a fully managed Memcached cloud that makes application caching simple, secure, and high-performing.

  • Apply updates in seconds with one click.
  • Get consistent performance and strong security on a private, dedicated infrastructure.

Free up your time and focus on building. 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 solid choice for most workloads, but you are welcome to adjust it as needed. To view all available instance types for Memcached, you can 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
    Spin up a real Memcached 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 Memcached

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