I read this article Picking a Development Strategy | Grav CMS about different approaches, but it is quite old and I think does not cover the “typical” usecases anymore. Uploading via FTP seems odd.
Typically deploying a PHP application uses a CI/CD pipeline nowdays. I use deployer for grav, that does work fine, but recently I was setting up a new PC where I pulled the repo from and installed everything.
I needed to run
composer install
bin/grav install
composer seems fine, grav install was ok, but now all my plugins are missing. So I have to run bin/gpm install admin now on all plugins again? I do still not get it. Maybe someone can bring light.
If it is up to the user how he handles that, It is rather user unfriendly 
@Micha1234,
Uploading via FTP seems odd.
You will be surprised how many Grav users on this forum are not developers and do not have ssh support on their shared hosting environment and have to fallback to FTP.
For many, their shared hosting server is the only server they have and do not even have a local dev environment.
The docs are quite suited for these users.
Experienced developers however are smart enough to setup more advanced alternatives.
but recently I was setting up a new PC where I pulled the repo from and installed everything.
“I pulled the repo from and installed”: Do you mean you pulled the repo from Github?
The repo does not contain anything beyond the very minimal required plugins and theme to run a bare Grav website.
So I have to run bin/gpm install admin now on all plugins again?
Yes… Admin and others are optional plugins and often not installed in production if not required.
Experienced devs will find their way…
1 Like
Experienced devs will find their way…
So you are saying you main audience is customers that
- Do not have any dev experience
- Do not use GIT to version their project
That seems not believable to me, since a lot of topic talk about extending things in Twig etc.
It seems the docs does simply not covering a professional way, why should I figure file and directory structure out for myself and any other dev should? This makes it not attractive for a quick setup.
I am happy to add a guide for such a setup, but just saying “Experienced devs will find their way…” is not helping anybody.
Started using GravCMS because I liked the idea of having everything in files, not in a complex DB.
1 Like