Steps after installing GitLab
DETAILS: Tier: Free, Premium, Ultimate Offering: Self-managed
Here are a few resources you might want to check out after completing the installation.
Email and notifications
- SMTP: Configure SMTP for proper email notifications support.
- Set up runners: Set up one or more GitLab Runners, the agents that are responsible for all of the GitLab CI/CD features.
- GitLab Pages: Configure GitLab Pages to allow hosting of static sites.
- GitLab Registry: Set up the GitLab container registry so every project can have its own space to store Docker images.
- GitLab Dependency Proxy: Set up the dependency proxy so you can cache container images from Docker Hub for faster, more reliable builds.
- Secure GitLab: Recommended practices to secure your GitLab instance.
- Sign up for the GitLab Security Newsletter to get notified for security updates upon release.
- LDAP: Configure LDAP to be used as an authentication mechanism for GitLab.
- SAML and OAuth: Authenticate via online services like Okta, Google, Azure AD, and more.
Backup and upgrade
- Back up and restore GitLab: Learn the different ways you can back up or restore GitLab.
- Upgrade GitLab: Every month, a new feature-rich GitLab version is released. Learn how to upgrade to it, or to an interim release that contains a security fix.
- Release and maintenance policy: Learn about GitLab policies governing version naming, as well as release pace for major, minor, patch, and security releases.
- Add a license or start a free trial: Activate all GitLab Enterprise Edition functionality with a license.
- Pricing: Pricing for the different tiers.
Cross-repository Code Search
- Advanced search: Leverage Elasticsearch or OpenSearch for faster, more advanced code search across your entire GitLab instance.
Scaling and replication
- Scaling GitLab: GitLab supports several different types of clustering.
- Geo replication: Geo is the solution for widely distributed development teams.
Install the product documentation
This is an optional step. If you want to host the documentation on your own server, see how to self-host the product documentation.