GitLab: 1. Authenticate

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 total flexibility.
• Effortless updates with just one click, so your environment stays 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 strong security on your own private, dedicated infrastructure. No noisy neighbours, 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.

The simplest way to get started is to log in through your browser. When you run the login command, the CLI opens a web page where you can approve access. No passwords or 2FA codes are entered directly into the CLI.

stackhero login

After logging in, your credentials are stored locally and will be used automatically by future CLI commands.

For fully automated environments such as scripts or CI pipelines, you may prefer a non-interactive access token. You can create one from your dashboard (Account > Access tokens), then export it as an environment variable. The CLI, as well as any script you run, will automatically detect it.

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