Opened 13 months ago
Closed 13 months ago
#3005 closed task (fixed)
FOSS4G Europe 2024 Domain
Reported by: | allixender | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Sysadmin Contract 2023-I |
Component: | SysAdmin | Keywords: | domain, website, conference |
Cc: |
Description (last modified by )
We would like the https://europe.foss4g.org/2024/ domain/subdomain to point to the current FOSS4G Europe event website. We have the website up and running as a GitHub Pages setup on https://landscapegeoinformatics.github.io/2024_foss4g_europe/ coming from that repository: https://github.com/LandscapeGeoinformatics/2024_foss4g_europe
I am not 100% sure how this can be achieved. Many former events' websites are hosted in the path addresses, e.g. /2017/ ... Is there a reverse proxy at work?
Update 23. Oct:
Shall alternatively be a URL considered as such https://2024.europe.foss4g.org ? We can rename the repository to 2024 and then this custom domain might work with GitHub pages directly?
Change History (7)
comment:1 by , 13 months ago
Description: | modified (diff) |
---|
comment:2 by , 13 months ago
Milestone: | Unplanned → Sysadmin Contract 2023-I |
---|
You can have both. Just give me a github.io domain and I can cname it to 2024.europe.foss4g.org and then use that for the /2024
comment:3 by , 13 months ago
Hi,
Thanks a lot for the advice. We reconfigured the GH pages like so:
https://2024-foss4g-europe.github.io/
So a CNAME 2024.europe.foss4g.org -> 2024-foss4g-europe.github.io ..
.. would be ideal.
Much appreciated.
Best, Alex
comment:4 by , 13 months ago
Okay I have it in place now, but it's giving a 404. I don't know if that is just a delay or something else needs changing. I verified I do have the cname set to 2024-foss4g-europe.github.io. As I recall, I think you have to put the 2024.europe.foss4g.org somewhere in the github settings for it to know to register an ssl. Once that is working, I'll make the change in europe.foss4g.org to show that instead of the current 2017 it is showing.
follow-up: 7 comment:5 by , 13 months ago
I think it works now:
https://2024.europe.foss4g.org/
I have added this domain into the GH pages config for the repo. You could now try to do the other forward/redirect if you see it stays stable.
I'd kindly like to ask to keep the issue open for a few more days to catch and fix little errors that might have slipped in.
Thanks a lot for the help.
Best, Alex
comment:6 by , 13 months ago
Would you recommend we verify the domain?
That would require to add an additional DNS TXT record.
comment:7 by , 13 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to allixender:
I think it works now:
https://2024.europe.foss4g.org/
I have added this domain into the GH pages config for the repo. You could now try to do the other forward/redirect if you see it stays stable.
I'd kindly like to ask to keep the issue open for a few more days to catch and fix little errors that might have slipped in.
Thanks a lot for the help.
Best, Alex
Done, I've added a redirect here to 2024.europe.foss4g.org
Would you recommend we verify the domain?
That would require to add an additional DNS TXT record.
I think it's more for the benefit of github than usage on website. I do it for long standing code projects like postgis, geos so people know that is the official repo.
If you want to do it, just let me know once you have the text to add and I'll add it. But like I said, I don't think it's necessary.
For now I'll close this ticket out since all seems to be working as expected.
Update 23. Oct:
Shall alternatively be a URL considered as such https://2024.europe.foss4g.org ? We can rename the repository to 2024 and then this custom domain might work with GitHub pages directly?