GitLab: 6. Change the configuration

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

👋 Welcome to the Stackhero documentation!

Stackhero offers a ready-to-use GitLab cloud solution designed for teams seeking a fast, secure, and scalable environment:

• Unlimited users, repositories, data transfers, and CI/CD processing time for complete flexibility.
• Effortless updates with a single click, keeping your environment up to date with no downtime.
• Custom domain name secured with HTTPS (for example, https://git.your-company.com) for a professional image and enhanced security.
• Consistent performance and robust security on your own private, dedicated infrastructure. No noisy neighbours and full isolation guaranteed.
• Choice of hosting location: 🇪🇺 Europe or 🇺🇸 USA to meet your compliance or latency requirements.

Get started quickly and focus on your code. Stackhero's GitLab cloud hosting solution is up and running in about 5 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 necessary)
stackhero service-configuration-set \
  --service=svc-xxxxxx \
  --configuration='{ "...": "..." }'

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

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