search

Segs / Segs.dev

For segs.io config, scripts, themes, and issues
BSD 3-Clause "New" or "Revised" License
2 stars 0 forks source link

Modify webserver config to handle new domain #8

Closed ldilley closed 5 years ago

ldilley commented 6 years ago

272 is dependent on this issue. The following problems remain:

1.) Need valid SSL certificate for *.segs.io (wildcard is now supported by Let's Encrypt). CloudFlare is currently complaining about the SSL certificate on the host being invalid for most requests (https://gitlab.segs.io/ for example). 2.) http://forum.segs.io/ currently forwards to top-level of nemerle.eu. The new domain is preserved. 3.) https://forum.segs.io/ sometimes forwards to GitLab. 4.) http://www.segs.io/ currently redirects to segs.nemerle.eu and does not preserve the new domain. 5.) http://segs.io/ and http://gitlab.segs.io/ currently go to the top-level of nemerle.eu and the new domain is preserved.

@nemerle has already started looking at the webserver config on his end and will tackle as time allows.

discord.segs.io, irc.segs.io, hook.segs.io, mail.segs.io, and test.segs.io are working as intended.

ldilley commented 6 years ago

Issues 1 and 4 have been resolved. forum.segs.io still goes to GitLab. segs.io and gitlab.segs.io still go to top level of nemerle.eu with the "hello" index.html.

broxen commented 6 years ago

What's the status here? Should we use the existing forum links?

ldilley commented 6 years ago

http://segs.io/ and http://forum.segs.io/ now work as intended as does GitLab. One step closer to 0.5.0...