Node.js: 6. Change the configuration
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 offers a ready-to-use Node.js cloud solution designed to help you move faster:
- Deploy to production in seconds with a simple
git push. No additional tools or manual configuration needed.- Use your own domain and take advantage of automatic HTTPS certificate setup, keeping your application secure with no extra steps.
- Enjoy automatic backups, one-click updates, and predictable, transparent pricing so you can focus on building features while Stackhero manages the infrastructure.
- Benefit from dedicated, private infrastructure for optimal performance and enhanced security.
Save time and simplify your operations: you can have your application running on Stackhero's Node.js cloud hosting in just a few minutes.
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.