Now that there is a vagrant box, we can set the folder to not be inside wp
content and things will always be a step shorter. No need to chown or chmod
anything, the folder will exist. Also this is just a sample config, it can
be ignored or changed yeah?
On Feb 20, 2014 7:42 AM, "Jörn Zaefferer" <notifications@github.com> wrote:

> In wp-config-sample.php:
>
> > @@ -63,6 +63,9 @@
> >  if ( !defined('ABSPATH') )
> >  	define('ABSPATH', dirname(__FILE__) . '/');
> >
> > +define( 'WP_CONTENT_DIR', dirname( ABSPATH ) . '/jquery-wp-content' );
> > +define( 'UPLOADS', dirname( ABSPATH ) . '/wordpress/uploads' );
>
>  Which means we have to tell the user to chmod 777 uploads
>
> That's actually what I had to do, and hub (git extension for GitHub)
> complains about the world writable dir everytime I use git inside my
> jquery-wp-content folder. An alternative solution would be welcome.
>
> If I remember correctly, the permission change was necessary to deploy
> sites that included any resources. Deploying posts/pages worked fine
> without that. Which makes sense, since those aren't uploads.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/jquery/jquery-wp-content/pull/292/files#r9910252>
> .
>