A copy of the Kirby Plainkit, but with a more secure public folder setup and a composer config for a custom path structure. That should be a good starting point, to create all kind of kirby projects and be able to do build to '/dist' or setup a backend-frontend-headless-structure ... whatever (build not included yet)
- Secure Public Folder Setup '/src/public'
- Composer installs Kirby to '/src/vendor'
- Composer installs Plugins to '/src/site/plugins'
- Composer starts local PHP Server in '/src/public'
- DotEnv by Beebmx\KirbyEnv
Kirby CMS https://getkirby.com
Kirby Plainkit https://github.com/getkirby/plainkit
Custom Folder Setup https://getkirby.com/docs/guide/configuration#custom-folder-setup
Custom Path https://getkirby.com/docs/cookbook/setup/composer#installing-kirby-to-a-custom-directory
DotEnv https://github.com/beebmx/kirby-env, https://github.com/johannschopplich/kirby-extended
Install composer: https://getcomposer.org/ or use homebrew
brew install composer
clone reposi tory
git clone git@github.com:dennisbaum/kirby3-plainkit-publicfolder-custompath.git
create .env by duplicate .env.example
cd kirby3-plainkit-publicfolder-custompath
cp src/.env.example src/.env
open in VSCode
code .
install Kirby and run Server
composer install
composer start
composer remove beebmx/kirby-env
composer require johannschopplich/kirby-extended
gitignore plugins installed by composer after updating to kirby-extended, you have to update the config.php to use dotenv again
rename '/src', change 'vendor-dir', 'kirby-plugin-path' and also change the folder where php starts the server in composer.json
Keep in mind that Kirby is not freeware. You can buy a licence: https://getkirby.com/buy -> It's worth it!