Jump to content

Git strategy for easy install by others


Recommended Posts


I'm working on a project that I'd like/hope will become a public open source project. I wonder - what is the best way to check in PW in git so that it's easy to install for others? I'm leaning towards checking in everything (including /wire), except /site/assets/file, /site/assets/cache and such. My hope is that someone could just git clone the project and copy the database to get going.

However, I know PW needs to go through the installer sometimes to work properly. I had instances where I needed to install it and then copy over the content/templates afterwards. Is there a way to automate an installer export after a git-hook perhaps?

How would you go about this? Thanks!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...