Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • omnibus-gitlab omnibus-gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 990
    • Issues 990
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 62
    • Merge requests 62
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Issues
  • #1096
Closed
Open
Created Feb 02, 2016 by Jeroen Jacobs@jeroenj

Support for Let's Encrypt automatically generated and renewed SSL certificates

It would be nice if GitLab installations came with Let's Encrypt SSL support by default.

While it isn't exactly a core concern of GitLab I think a lot of people use the omnibus package to set up GitLab on a single host and configure SSL manually afterwards.

A rough idea is that the certificate gets created during the Chef run and that a cron job is provided which renews the certificate if needed.

This Digital Ocean tutorial might provide an example of how it could be implemented with nginx.

I'm currently looking into automating some SSL stuff at work. I might look into this if I find some time and if there is any interest in it. :)

Assignee
Assign to
Time tracking