cravaus wrote on Friday, August 26, 2016:
Synology has moved over to Ngnix. However pices of Apache still work. Apparently I can run .htaccess files but not every thing will work there for example I cannot do a http to https redirect there, I have to do that in Ngnix, but I can redirect from www.mydomain.com to www.mydomain.com/wordpress in .htaccess. I am not sure about all the restrictions but it appears to be only partially compliant.
OpenEMR runs. I am wondering about the slice of instructions we normally put into my Appache config (my mods for Synology here,[User] is replaced the user name):
<Directory "/volume1/homes/[User]/www/openemr">
AllowOverride FileInfo
</Directory>
<Directory "/volume1/homes/[User]/www/openemr/sites">
AllowOverride None
</Directory>
<Directory "/volume1/homes/[User]/www/openemr/sites/*/documents">
order deny,allow
Deny from all
</Directory>
<Directory "/volume1/homes/[User]/www/openemr/sites/*/edi">
order deny,allow
Deny from all
</Directory>
<Directory "/volume1/homes/[User]/www/openemr/sites/*/era">
order deny,allow
Deny from all
</Directory>
I have pasted this in the config but I have no idea if it is doing anything now in the new system for Synology. OpenEMR runs regardless of this being in the apache config now. How would I test this. Or, better, how can I put the equivalent into the Ngnix config (/usr/syno/share/nginx/WWWService.mustache). This is where I am doing my redirects for https so I would suppose this is where I would add this. What would be the equivalent here?