Replies: 2 comments
-
Enabled debug mode and compared to the demo site: I do believe the issue is with Herd/Valet and the way it proxies websites. I haven't got the time to debug just now, but will come back to it. |
Beta Was this translation helpful? Give feedback.
-
Hi there, thanks for reaching out. Such detailed feedback is really helpful! The issue here is that Valet is creating quite a mess with setting the The point is that when defining server vars, here with Nginx, it is not advised to just add them but with an empty string as value since other apps that are not build with Laravel might actually be dependent on a correctly configured server. When I recall it correctly, Laravel doesn't use Automad first checks for the existence of the I have pushed a minor change to only use |
Beta Was this translation helpful? Give feedback.
-
First of all: amazing work on Automad. I got to play with the demo version a bit and really love the design.
Some background on my issue: I am using Herd (Pro) and tried to quickly spin up Automad CMS 2.0 today but I am unable to access /dashboard. I tried re-setting the permissions on files & folders (644 and 755) unsuccessfully. I also tried to add
"AM_BASE_URL": "https://automad.test"
inside config.php and a few other things and were not able to get it running.I will come back once 2.0 final version is released and give it another go. If you have any ideas on what might be wrong please let me know and I am happy to test. I am not sure if it's a compatibility issue with Herd Pro or of it's something else.
Beta Was this translation helpful? Give feedback.
All reactions