Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#2096 closed task (fixed)

FOSS4G-Europe 2018 Conference website

Reported by: jgrocha Owned by: sac@…
Priority: major Milestone:
Component: Systems Admin Keywords:



The FOSS4G-Europe 2018 LOC team already setup a Wordpress based website for the conference, on their own server, with the URL: It is a Ubuntu based server, running Apache.

To make the URLs consistent for every FOSS4G-Europe conference, we would like to have: pointing to:

If any changes are needed on the LOC server, we are glad to help.


Jorge Gustavo

Change History (6)

comment:1 Changed 3 years ago by wildintellect

What url would you like users to see? ​ Either way the edits required need to happen on the server that hosts, which appears to be the Webextra VM.

Option 1 is a Proxy or Rewrite ​ Option 2 is a Redirect ​

comment:2 Changed 3 years ago by jgrocha


A redirect is enough.


Jorge Gustavo

comment:3 Changed 3 years ago by jsanz

Priority: normalmajor


Having a totally different domain for FOSS4G Europe than other years is a bit confusing, but at least that redirect should be put in place so and redirect to

That way we would be pretty sure to "capture" the people willing to know more about the event.

I'm allowing myself to mark this issue as major because the event is not that far away and the local team are already very active and need all the help the Foundation can give.


comment:4 Changed 3 years ago by robe

I noticed that redirects to 2017 at moment, so that default redirect should also be changed.

I also notice the apache configs for webextra are in git, but has no git remote, side note we should probably put this in gitea.

I'd be happy to do all of this but I don't have sudo rights to webextra server, so I can only read the configs and know what needs changing.

comment:5 Changed 3 years ago by strk

Resolution: fixed
Status: newclosed

Done. I proxied to, the server itself does redirect from http to https. Please reopen if you think https should be proxied directly instead (requires adding a new apache directive to enable that)

comment:6 Changed 3 years ago by strk

For the record: I did change config to proxy https directly, so to avoid having a round-trip and a change of URL (.pt server would redirect thus changing user URL).

BTW, I noticed that depending on how you access the server (http or https) you get a different banner image. The HTTPS one has a knight on the left which is not shown in HTTP, is this intentional ? (fun)

Note: See TracTickets for help on using tickets.