How does the plugin handle certificate renewals?

[asarkar]

...no mention of renewals in the doc.

[JustinAiken]

Afraid there's not really much of a renewal process... every 90 days or so you have to do the jekyll letsencrypt dance from scratch. If Gitlab had an API endpoint to post the new certs, it could be fully automated and stashed in a cron job.

[asarkar]

I moved to Netlify. They have everything I need for free, and I can keep the blog on GitHub (though not as GH Pages). GitLab has around 10k bugs open, which doesn't say much about the quality control, and their deploy fails randomly.

[b-long]

@JustinAiken Couldn't renewal be automated using the cron-like Pipeline scheduling in GitLab ?

More info: https://docs.gitlab.com/ce/user/project/pipelines/schedules.html

I think if possible, your code and the workflow would be valuable to a wide variety of people.

[JustinAiken]

The problem is, it could run automatically in the cronish Pipeline to generate a new certificate... but it wouldn't get entered in. One must still manually go to the domains page, delete the domain, then readd it with the freshly-generated certificate..

[b-long]

Ah, I see. My mistake.