Fixes #38752 - Guide for HTTPs in DEV environment

[stejskalleos]

No description provided.

[stejskalleos]

@arvind4501

[evgeni]

I had a short dejavu, but then realized the last iteration of this was posted on Discourse, not in the dev docs:

https://community.theforeman.org/t/setting-up-ssl-for-running-foreman-on-https/36168

[ekohl]

Thanks @evgeni for that post. I was looking for my notes on playing with Puma & HTTPS (without Apache in front). I think that's still something to investigate because we can look at using HTTPS out of the box in development.

[stejskalleos]

I was looking for my notes on playing with Puma & HTTPS (without Apache in front).

Could you share your notes & insights?
I'm not opposed to the idea of excluding the httpd proxy, but I'm unsure what the benefits are compared to this approach.

I'll gladly investigate other options; any hints or suggestions are welcome.

[ekohl]

It's in the post that was shared before: https://community.theforeman.org/t/setting-up-ssl-for-running-foreman-on-https/36168/5

Benefit is that you don't need anything external: no Apache to set up. By using https://rubygems.org/gems/localhost you can also avoid mkcert. In other words, no root access needed. That means we can even make it the default devel setup because we can make git clone && bundle install && bundle exec foreman start work (with https).

Downside is that there are a few minor code tweaks we'd need to make but I think they'd be minor.