element-hq
Missing Apache config
Your use case
Some may want to run element-call on Apache server. Therefore, it would be helpful to have a working configuration for this (in the config folder), esp. with respect to route any requests to non-existing paths back to /index.html.
Have you considered any alternatives?
No response
Additional context
No response
Personally I don't feel good about providing configs for every web server under the sun: they are likely to get out of date. If people want to use different web servers, I would assume they generally know how to configure them correctly.
"According to W3Techs’ data, Nginx holds about 34.2% of the market and Apache about 31.2% — 28.9% and 22.6% respectively according to Netcraft’s data." ( see https://www.stackscale.com/blog/top-web-servers/).
So I wasn't suggesting to add a config for any server under the sun.
Providing one for Nginx and none for Apache is at least questionable.
We only have an nginx config because it's what's used in the docker image - it's not a question of deciding to give a config for one web server and not another.
Below are a few rewrites added to a local .htaccess within the Element Call root folder that seems to work for me. Maybe one should add this or something similar too.
RewriteEngine On
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} -f [OR]
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} -d
RewriteRule ^ - [L]
RewriteRule . /index.html [L]
Thanks, that lets pages at /room/ load properly when visited directly or refreshed.
