Setting up Pimcore for core contribution #17021
-
Maybe it's on me and I cannot use Google or read docs anymore, but I didn't find any way to set up Pimcore for "Core Development" 🤔 I'd like to contribute a small Feature to Pimcore but didn't find any way to get started setting up Pimcore from the Unfortunately, the Am I missing something obvious? Can anyone help me out here? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
I am using Pimcore for 12 years now and made 100 of contributions and I still don't know what the Pimcore way of dealing with that is. I believe they just set up the skeleton and install pimcore/pimcore in a lib folder and use composer repositories to link it to that path. With that you can then also install all other non core bundles like Admin or Studio. But that still is a hideous task to setup and also quite error prone. I ended up using pimcore/pimcore and just changing code, that I don't commit, to make it work. I would love to have a separate documentation and Pimcore's views on how they handle it. PS: with CoreShop you can just clone the repo, start docker and you are good to go. Makes it super easy to use setup and develop. |
Beta Was this translation helpful? Give feedback.
-
Hi, Cheers... |
Beta Was this translation helpful? Give feedback.
-
Interesting approach 👍🏼 I used following composer.json setting to load the pimcore packages from source:
Then I can add the fork repositories as remote and make changes directly in vendor/pimcore/*. |
Beta Was this translation helpful? Give feedback.
Hi,
we use our demo repository.
Just install the demo as described, then clone your forks of the pimcore repositories you want to contribute to into
dev/pimcore/*
and runcomposer update
.Then, composer should symlink the repositories instead of downloading them into vendor folder and you can make your changes, test them and create PRs. The key part is here in composer.json.
Cheers...