search

humanmade / Salty-WordPress

A flavorful way to manage your entire WordPress stack.
126 stars 22 forks source link

Don't download and install WordPress trunk by default #96

Open rmccue opened 10 years ago

rmccue commented 10 years ago

If you're setting up Salty purely for a specific project, you have to sit through the cloning of WP core into wordpress-trunk.dev even if you aren't ever going to use it.

joehoyle commented 10 years ago

Perhaps we could just download wordpress-latest.zip and put that in. I think it's good to have a demo site in there to test against etc. — Sent from Mailbox

On Thu, Jul 24, 2014 at 12:27 AM, Ryan McCue notifications@github.com wrote:

If you're setting up Salty purely for a specific project, you have to sit through the cloning of WP core into wordpress-trunk.dev even if you aren't ever going to use it.

Reply to this email directly or view it on GitHub: https://github.com/humanmade/Salty-WordPress/issues/96

mattheu commented 10 years ago

Can we use --depth=1 so that it doesn't clone the whole history - this is much quicker.

Matt

On 24 July 2014 09:09, Joe Hoyle notifications@github.com wrote:

Perhaps we could just download wordpress-latest.zip and put that in. I think it's good to have a demo site in there to test against etc. — Sent from Mailbox

On Thu, Jul 24, 2014 at 12:27 AM, Ryan McCue notifications@github.com wrote:

If you're setting up Salty purely for a specific project, you have to sit through the cloning of WP core into wordpress-trunk.dev even if you

aren't ever going to use it.

Reply to this email directly or view it on GitHub: https://github.com/humanmade/Salty-WordPress/issues/96

— Reply to this email directly or view it on GitHub https://github.com/humanmade/Salty-WordPress/issues/96#issuecomment-49978901 .

Matthew Haines-Young Human Made Limited Email: matthew@humanmade.co.uk Skype: matthewhainesyoung Tel: +44 7929 183 298

joehoyle commented 10 years ago

I think it’s an svn repo

mattheu commented 10 years ago

Ah - in which case we could switch to the git mirror ;)

rmccue commented 10 years ago

Ah - in which case we could switch to the git mirror ;)

Git is going to be waaaay slower, even with --depth=1.

I think a better situation would be simply to note in the readme how to set up wordpress-trunk.dev if you want to.

danielbachhuber commented 10 years ago

I think a better situation would be simply to note in the readme how to set up wordpress-trunk.dev if you want to.

I use wordpress-trunk.dev on a pretty regular basis. I think you might be solving a problem only you have — Salty WordPress originally was intended to support all of the projects you're working on.

rmccue commented 10 years ago

I think you might be solving a problem only you have — Salty WordPress originally was intended to support all of the projects you're working on.

Right, but if I'm not working on wordpress-trunk.dev, it's not really one of my projects. :) IMO, the projects section should be customisable for users, and shouldn't assume that you're necessarily working on one project or another.

danielbachhuber commented 9 years ago

Related #104

paulgibbs commented 9 years ago

I just ran into this setting up Salty WP for the first time. It took ages for the wordpress trunk to clone; I think setting depth=1 would make it a little quicker, and worth doing while this discussion carries on.

danielbachhuber commented 9 years ago

I think setting depth=1 would make it a little quicker, and worth doing while this discussion carries on.

This was blocked by a feature request to Salt: https://github.com/saltstack/salt/issues/16920

However, it appears it's been implemented and isn't clear whether it's been released.