TimescaleDB: 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 TimescaleDB 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 ready-to-use TimescaleDB cloud solution designed to help you get up and running in minutes. Here is what you can look forward to:

  • All the best plugins included, such as PostGIS, PgVector, and more.
  • Convenient access to the PgAdmin web UI for easy database management.
  • Simple, one-click updates to keep your deployment current.
  • Reliable performance and strong security on your own private, dedicated infrastructure.

If you are looking to save time and streamline your workflow, Stackhero's TimescaleDB cloud hosting is designed to make your experience as smooth as possible. You can try it out in as little as 5 minutes!

The examples below use the entry-level instance 10G for TimescaleDB 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 TimescaleDB, you can 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
    Spin up a real TimescaleDB 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 TimescaleDB

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