I like how the #halcyon docs say "Apache: Just upload it, it works" and nothing works. </s> 🖕
@lerk Maybe you have a link to the instance so that I can look for the error?There are some server-wide dependencies named in the docs which should also be installed when using Apache.The rewrites are done using the .htaccess file in Apache which is in the document_root and should be automatically used.If the .htaccess is ignored,you have to enable it using AllowOverride all in the vHost config.
@halcyon aah, so there IS something to be changed when using Apache.
I was just about to send you a link to the rewrite rules I just wrote but I assume that is unnecessary when using the htaccess file (right?).
@halcyon just fyi, it also works when manually rewriting all the NGINX rewrite rules for apache.
@lerk The problem is that there might come additional rewrite rules with new Halcyon versions.Whenever there are new pages,there must also be new rewrite rules.The .htaccess is within the document root so a new .htaccess is applied automatically while the Nginx config has to be updated manually.That's what many admins unfortunately forget sometimes so I'm really happy that Apache provides an easier way.
@lerk I don't know a way to do that but I have to admit that I never worked with Nginx.My development instance runs on a Apache-based freehoster and my production instance runs on lighttpd where it's definitely not possible.If you know a way to make use of the .htaccess,feel free to send me your solution.And I'll add that AllowOverride all for Apache to my documentation.
@halcyon Apparently AllowOverride is directory based so the "AllowOverride all" has to be in the "<Directory>"-block rather than the "<VirtualHost>"-block.
@halcyon "This instance does not exist."
@lerk I updated the documentation page.If it doesn't find the instance,there could be something wrong with cURL.Is it installed and enabled in your php.ini?Maybe enabling the debug_mode in your config/config.ini will give you more information.
@halcyon ahahaha, no, ansible fucked up templating the config file because of the dual curly braces used in the who to follow link.
Interesting error message though.
@lerk If something fails in the authentication process,Halcyon always thinks there's something wrong with the Mastodon instance because it doesn't validate its own config and just expects it to be correct.But I assume it's working now?Great!
@halcyon partially. I still have to fix ansible fuckups.
Thanks a lot for your help :)
Mastodon server for anyone interested in CSS or general web development