TimescaleDB: 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 TimescaleDB 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 ready-to-use TimescaleDB cloud solution designed to get you started within minutes. Here’s what you can expect:

  • All the top plugins included, such as PostGIS, PgVector, and many more.
  • Convenient access to the PgAdmin web interface for straightforward database management.
  • Simple, one-click updates to keep your deployment up to date.
  • Reliable performance and enhanced security on your own private, dedicated infrastructure.

If you are looking to save time and simplify your processes, Stackhero’s TimescaleDB cloud hosting is designed to make your experience as seamless as possible. You can try it out in just 5 minutes!

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

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

Continue reading this guide

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

  1. Automate with the CLI
    Start TimescaleDB, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI