title

Infrastructure Environments | The GitLab Handbook

charset

utf-8

viewport

width=device-width, initial-scale=1, shrink-to-fit=no

robots

index, follow

theme-color

#6e49cb

og:title

Infrastructure Environments

og:description

Learn more about GitLab and what makes us tick.

og:type

website

og:url

https://handbook.gitlab.com/handbook/engineering/infrastructure/environments/

og:image

https://handbook.gitlab.com/images/gitlab-cover.png

twitter:card

summary_large_image

twitter:image

https://handbook.gitlab.com/images/gitlab-cover.png

twitter:title

Infrastructure Environments

twitter:description

Environments The Terraform configuration for the environments can be found in config-mgmt. Future Iteration with Infrastructure Standards We have a WIP initiative to iterate on our company-wide infrastructure standards. You can learn more about this on the infrastructure standards handbook page. This page will be refactored incrementally as the standards are documented, implemented, and changes to environments take place. Development Name URL Purpose Deploy Database Terminal access Development various Development on save Fixture individual dev Development happens on a local machine. Therefore there is no way to provide any SLA. Access is to the individual dev. This could be either EE/CE depending on what the developer is working on.

twitter:site

@GitLab

name

Infrastructure Environments

description

Environments The Terraform configuration for the environments can be found in config-mgmt. Future Iteration with Infrastructure Standards We have a WIP initiative to iterate on our company-wide infrastructure standards. You can learn more about this on the infrastructure standards handbook page. This page will be refactored incrementally as the standards are documented, implemented, and changes to environments take place. Development Name URL Purpose Deploy Database Terminal access Development various Development on save Fixture individual dev Development happens on a local machine. Therefore there is no way to provide any SLA. Access is to the individual dev. This could be either EE/CE depending on what the developer is working on.

dateModified

2024-10-02T15:36:33+00:00

wordCount

1674

image

https://handbook.gitlab.com/images/gitlab-cover.png

apple-touch-icon

https://handbook.gitlab.com/favicons/favicon-1024x1024.png

canonical

https://handbook.gitlab.com/handbook/engineering/infrastructure/environments/

favicon

https://handbook.gitlab.com/favicons/favicon-152x152.png

favicon

https://handbook.gitlab.com/favicons/favicon-167x167.png

favicon

https://handbook.gitlab.com/favicons/favicon-180x180.png