Mercure-Hub: 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 Mercure Hub 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 Mercure-Hub cloud service, designed to simplify and ensure reliable real-time data delivery. You benefit from:

  • Unlimited requests and message sizes for complete flexibility.
  • A custom domain with integrated HTTPS security (for example, https://real-time.your-company.com).
  • One-click updates to keep your hub up to date effortlessly.
  • High performance and enhanced security on a private, dedicated infrastructure.
  • Multiple available regions: 🇪🇺 Europe and 🇺🇸 USA for low-latency delivery.

Get started quickly: it takes just 5 minutes to launch your Mercure-Hub cloud hosting environment and start sending real-time updates to your applications.

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

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

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Launch a real Mercure Hub 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 Mercure-Hub

  1. Getting started
    How to get started with Mercure-hub
  2. Automate with the CLI
    Start Mercure Hub, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI