Public folder set up, missing kirby in path?

Kirby 3 Solved ✅
1

Following Configuration | Kirby CMS to set up Kirby above webroot threw a lot of errors. I assume this might be a typo?

include __DIR__ . '/../vendor/autoload.php';

and should be

include __DIR__ . '/../kirby/vendor/autoload.php';

?

That is, if you keep the kirby folder as it is, this is what works for me in a local mamp set up:

- content
- kirby
- site
- public_html
   - assets
   - media
   - index.php
2

It depends on the setup. I think the first is correct for a composer based setup.

3

Isn’t that a bit confusing? It says:

In our Starterkit, we offer a flat setup that installs all folders directly in the document root of your server.

No word about composer or the way Kirby is installed.

4

Yes, it makes sense to fix it. Was just trying to figure out why that path was used.

5

Ok, thanks (It’s a shame if people get discouraged by the errors to not implement this)

6

I already fixed it, unfortunately, some things slip through unnoticed.

7

:+1: