title

Why we use Ruby on Rails to build GitLab

charset

utf-8

viewport

width=device-width,initial-scale=1

Content-Security-Policy

default-src 'self' https: http:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https: http: *.googletagmanager.com; style-src 'self' 'unsafe-inline' https: http: https://fonts.googleapis.com; object-src https: http:; base-uri 'self'; connect-src 'self' https: http: wss: ws: *.google-analytics.com *.analytics.google.com *.googletagmanager.com; frame-src 'self' https: http:; img-src 'self' https: http: data: *.google-analytics.com *.googletagmanager.com; manifest-src 'self'; media-src 'self' https: http:; child-src 'self' blob: https: http:; font-src 'self' https: http: data: https://fonts.gstatic.com;

format-detection

telephone=no

og:title

Why we use Ruby on Rails to build GitLab

og:description

Here's our CEO on GitLab’s inception using Rails, and how challenges are being handled along the way.

og:image

https://images.ctfassets.net/r9o86ar0p03f/gitlab-ruby.jpg/2410e971cd4362d087948f7eeea512d4/gitlab-ruby.jpg?fm=webp&w=820&h=500

og:url

https://about.gitlab.com/blog/2018/10/29/why-we-use-rails-to-build-gitlab/

og:type

article

twitter:card

summary_large_image

twitter:site

@GitLab

alternate

/atom.xml

alternate

/all-releases.xml

alternate

/security-releases.xml

alternate

/releases.xml

apple-touch-icon

/blog/nuxt-images/ico/apple-touch-icon-57x57.png?cache=2022041

x-default

https://about.gitlab.com/blog/2018/10/29/why-we-use-rails-to-build-gitlab/