Node.js: 4. Create the service

This documentation is part of the Automate with the CLI guide. You can view the complete guide here: Start Node.js, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI.

👋 Welcome to the Stackhero documentation!

Stackhero provides a ready-to-use Node.js cloud solution designed to help you move faster:

• Deploy your application to production in seconds with a simple git push. No additional tools or manual configuration required.
• Use your own domain and benefit from automatic HTTPS certificate setup, ensuring your application is secure without any extra steps.
• Enjoy automatic backups, one-click updates, and clear, predictable pricing so you can focus on developing features while Stackhero manages the infrastructure.
• Experience optimal performance and enhanced security thanks to a private, dedicated VM.

Save time and simplify your operations: it only takes a few minutes to try out Stackhero's Node.js cloud hosting solution!

Below is an example script that creates a stack, adds your Node.js service to it, waits for it to start, retrieves its configuration (including generated credentials), and then applies a new configuration.

#!/bin/bash
set -e

export STACKHERO_TOKEN="usr-xxxxxx:your-token"

serviceStore="node-js"   # The Node.js service store name (see step 2)
instance="..."                # An instance size from step 3
region="europe"               # A region name from step 3

# Create a stack for your service (uses your default organisation; add --organization if needed)
stackId=$(stackhero --format=script stack-create \
  --name="My Node.js stack")
echo "Stack created: ${stackId}"

# Add Node.js to the stack (names are resolved automatically)
serviceId=$(stackhero --format=script service-add \
  --stack="My Node.js stack" \
  --service-store="${serviceStore}" \
  --instance="${instance}" \
  --region="${region}")
echo "Service added: node-js"

# Wait for the service to be fully operational (this may take a few minutes)
stackhero service-wait-for --service="node-js"

# Retrieve the service configuration, including generated credentials
stackhero service-configuration-get --service="node-js" --format=json