There is much written here in this forum, as well as on the support docs and reference books on
https://getkirby.com/docs/ but I wanted to share some info and ask a few questions about local setup, of which there are a gazillion flavors. Some prefer the command line, but I prefer methods that lend to the ease of use of my clients which is a big concern in my case.
So, in my case, I’ve traveled down a few paths using Valet via command line, MAMP gui, VSCode plugins for compiling sass, et al, as well as using my current setup:
- VSCode (no plugin compiling)
- CodeKit (for compiling)
- GitHub Desktop or CL
- MAMP / Pro
- plus browsers.
- Content managed via Kirby Panel.
Also, I’ve started including Kirby as a submodule in my GitHub repository. It’s possible that I could include plugins the same way, but I haven’t gone that far.
I’d love any comment from you (since you kindly clicked on this topic) that specifically addresses the pros or cons about your setup, beyond the flavors mentioned in the Local Dev Docs:
I’d love to hear people share the Hows and Whys and what they solve by doing it that way.
Please mention options you use specific to your setup, such as directing CodeKit to ignore certain files or folders, or adding items into the .gitignore file, or adding in submodules to your GitHub repo.
All info is welcome, especially if it is specific, and hopefully any info shared here can be added to the article above if needed.
Cheers and happy coding/designing!