Node-RED: 6. Change the configuration

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

Welcome to the Stackhero documentation

Stackhero offers a fully managed Node-RED cloud environment designed to help you build workflows quickly:

• Integrated MQTT server (Mosquitto) for seamless IoT integration.
• Full access to the Node-RED admin interface for managing your flows and settings.
• Node-RED Dashboard included for real-time visualization.
• Dedicated SMTP email server included, with no sending limits.
• Effortless one-click updates to easily keep your instance up to date.
• Custom domain names with automatic HTTPS: for example, https://node-red.your-company.com.
• High performance and enhanced security thanks to private, dedicated infrastructure.

You can have a secure, production-ready Node-RED cloud hosting instance up and running in about 5 minutes. Stackhero takes care of installation, updates, and infrastructure so you can focus on building your automations.

You can review an example configuration schema and then apply your own settings. When you update the configuration, the service may restart to apply the changes.

# View the configuration schema and an example for your service
stackhero service-configuration-example --service=svc-xxxxxx

# Apply a custom configuration (the service restarts if needed)
stackhero service-configuration-set \
  --service=svc-xxxxxx \
  --configuration='{ "...": "..." }'

# Wait for the new configuration to be applied
stackhero service-wait-for --service=svc-xxxxxx

That's it. You have now seen the full lifecycle: start a service, retrieve its credentials, and reconfigure it, all in a scriptable, automated way. To learn more, refer to the full CLI documentation, which also covers the non-interactive STACKHERO_TOKEN authentication demonstrated here.