5 ms·

I'm one of the creators of this (we're the same people behind http://roots.io http://roots.io) so I'm happy to answer any questions. We're just trying to make d

I'm one of the creators of this (we're the same people behind http://roots.io http://roots.io) so I'm happy to answer any questions. We're just trying to make developing WordPress sites a little more bearable :)

codelust 13y ago
Congrats. This looks pretty neat, especially since it uses Composer. Does it do the whole autoloader song and dance with Composer? Example: If I add Guzzle to Composer, can I call it from my plugin's code the way you can with other frameworks? Only thing I would change is to swap out Capistrano with Fabric. But that's a personal choice.
- bretthopper 13y ago
  The autoloader is required in wp-config to get access to Dotenv: https://github.com/roots/bedrock/blob/master/wp-config.php#L7 https://github.com/roots/bedrock/blob/master/wp-config.php#L... But in the example you gave, ideally your custom plugin is itself a Composer package which requires Guzzle in its composer.json file. Then you'd require your plugin in the project's composer.json :) Re: Capistrano. We're really trying to encourage people to fork this and modify it to their needs. So you could easily rip Cap out and integrate Fabric in your own fork. We're just providing some sensible defaults that we're familiar with.
- squigs25 13y ago
  nice pun: "song and dance with Composer"
- rmccue 13y ago
  I know it's just an example, but: if you're doing HTTP in WordPress, please use WP HTTP rather than Guzzle. It has compatibility with many more hosts (since it uses sockets as well as cURL), plus it's already built-in.
Xdes 13y ago
Hi, I have not written a single of line of php. How hard would it be to get started with a Ruby/Node/.NET background?
- bretthopper 13y ago
  WordPress is known for being "easy" but that depends on what you want to do with it. It's definitely easy to get a simple blog up and running since it's mostly done for you. But WP can quickly get complicated since it isn't designed well and the documentation is pretty bad surprisingly. There's a ton of resources online but the quality of it is hit and miss.
- chc 13y ago
  PHP isn't the most fun language, but it's not that hard either. It's unusually quirky, but not unusable. As for WordPress, though — if you're used to a nice, sane API like you get in Rails or .NET, you're probably going to find the massive heap of cruft that we call WordPress a little bit aggravating.
  - krapp 13y ago
    Yes, it's probably worth mentioning that even people willing to deal with PHP find Wordpress code to be 'aggravating'. It is, unfortunately, not an example of PHP application design at its best... Upshot, though, there's plenty of documentation and SO threads out there and a huge ecosystem of plugins. Most of the time you never even need to look at the actual source code.
    - smacktoward 13y ago
      And in the WordPress core developers' defense, it has been getting steadily better as time goes on. It's still a long way from perfect, of course, but they're working on it.
      - krapp 13y ago
        things like this need to stop though: <?php /* pointless comment */ ?> <?php echo $something; ?><div><?php if($blah){ echo stuff(); ?></div><?php } ?>... ...keeping track of that context switching in a complex theme can be maddening. Especially if it includes inline css and javascript or (heavens forfend) mixes php in with the inline css and javascript...
MPetitt 13y ago
Will updating Wordpress be the same as usual, or will we have to modify/get custom builds?
- bretthopper 13y ago
  Updating WP is just a matter of bumping the version in the composer.json file and running `composer update`. We believe it's better to manually do this and be explicit about it rather than letting WP update itself. This way you can quickly just look in the composer.json to see the versions of everything being used (WP, plugins, etc).
  - pan69 13y ago
    "composer update" maybe? "composer install" will install from composer.lock.
  - bretthopper 13y ago
    pan69: correct. Updated my reply to fix that.
mikegirouard 13y ago
This looks like a much more formalized structure than what we do. Do you use it in production currently or is this a prototype? This is my primary new WP project approach (which isn't perfect): mkdir Example-Project cd Example-Project # Grab the latest wordpress, www is our DocumentRoot curl wordpress.org/latest.tar.gz | tar -xvz -- mv wordpress www cd www # Drop the default wp-content and symlink so we dont need to # keep all of wp in Git mv wp-content .. ln -s ../wp-content echo 'www/' >> .gitignore # Make the repo git init git add . && git commit -m 'First!' The main problem I run into is with the symlink'd wp-content directory. WP seems to not interpret it well and I have to set up Alias directives in the virtualhost configuration to compensate. Are you doing anything similar with the app/ directory?
- bretthopper 13y ago
  It's being used in production for roots.io right now but it's still a work in progress. Seems like your issue has to do with your symlink setup. We don't need to do any special configuration with the web server. Here's the configuration that deals with app/: https://github.com/roots/bedrock/blob/master/config/application.php#L25-L27 https://github.com/roots/bedrock/blob/master/config/applicat...
- pestaa 13y ago
  I believe you're missing Options +FollowSymLinks from your Apache configuration and is not a problem with WP actually.
csomar 13y ago
Are you hiring freelancers/contractors?
- bretthopper 13y ago
  Roots isn't actually a "company". Just an open source organization although we do sell a few things like screencasts. If you're interested in work to do with WP/Roots you can check out this thread on our forum: http://discourse.roots.io/t/looking-for-work-post-your-info-here/743 http://discourse.roots.io/t/looking-for-work-post-your-info-...

codelust 13y ago

Congrats. This looks pretty neat, especially since it uses Composer. Does it do the whole autoloader song and dance with Composer? Example: If I add Guzzle to Composer, can I call it from my plugin's code the way you can with other frameworks? Only thing I would change is to swap out Capistrano with Fabric. But that's a personal choice.

bretthopper 13y ago
The autoloader is required in wp-config to get access to Dotenv: https://github.com/roots/bedrock/blob/master/wp-config.php#L7 https://github.com/roots/bedrock/blob/master/wp-config.php#L... But in the example you gave, ideally your custom plugin is itself a Composer package which requires Guzzle in its composer.json file. Then you'd require your plugin in the project's composer.json :) Re: Capistrano. We're really trying to encourage people to fork this and modify it to their needs. So you could easily rip Cap out and integrate Fabric in your own fork. We're just providing some sensible defaults that we're familiar with.
squigs25 13y ago
nice pun: "song and dance with Composer"
rmccue 13y ago
I know it's just an example, but: if you're doing HTTP in WordPress, please use WP HTTP rather than Guzzle. It has compatibility with many more hosts (since it uses sockets as well as cURL), plus it's already built-in.

Xdes 13y ago

Hi, I have not written a single of line of php. How hard would it be to get started with a Ruby/Node/.NET background?

bretthopper 13y ago
WordPress is known for being "easy" but that depends on what you want to do with it. It's definitely easy to get a simple blog up and running since it's mostly done for you. But WP can quickly get complicated since it isn't designed well and the documentation is pretty bad surprisingly. There's a ton of resources online but the quality of it is hit and miss.
chc 13y ago
PHP isn't the most fun language, but it's not that hard either. It's unusually quirky, but not unusable. As for WordPress, though — if you're used to a nice, sane API like you get in Rails or .NET, you're probably going to find the massive heap of cruft that we call WordPress a little bit aggravating.
- krapp 13y ago
  Yes, it's probably worth mentioning that even people willing to deal with PHP find Wordpress code to be 'aggravating'. It is, unfortunately, not an example of PHP application design at its best... Upshot, though, there's plenty of documentation and SO threads out there and a huge ecosystem of plugins. Most of the time you never even need to look at the actual source code.
  - smacktoward 13y ago
    And in the WordPress core developers' defense, it has been getting steadily better as time goes on. It's still a long way from perfect, of course, but they're working on it.
    - krapp 13y ago
      things like this need to stop though: <?php /* pointless comment */ ?> <?php echo $something; ?><div><?php if($blah){ echo stuff(); ?></div><?php } ?>... ...keeping track of that context switching in a complex theme can be maddening. Especially if it includes inline css and javascript or (heavens forfend) mixes php in with the inline css and javascript...

MPetitt 13y ago

Will updating Wordpress be the same as usual, or will we have to modify/get custom builds?

bretthopper 13y ago
Updating WP is just a matter of bumping the version in the composer.json file and running `composer update`. We believe it's better to manually do this and be explicit about it rather than letting WP update itself. This way you can quickly just look in the composer.json to see the versions of everything being used (WP, plugins, etc).
- pan69 13y ago
  "composer update" maybe? "composer install" will install from composer.lock.
- bretthopper 13y ago
  pan69: correct. Updated my reply to fix that.

mikegirouard 13y ago

This looks like a much more formalized structure than what we do. Do you use it in production currently or is this a prototype? This is my primary new WP project approach (which isn't perfect): mkdir Example-Project cd Example-Project # Grab the latest wordpress, www is our DocumentRoot curl wordpress.org/latest.tar.gz | tar -xvz -- mv wordpress www cd www # Drop the default wp-content and symlink so we dont need to # keep all of wp in Git mv wp-content .. ln -s ../wp-content echo 'www/' >> .gitignore # Make the repo git init git add . && git commit -m 'First!' The main problem I run into is with the symlink'd wp-content directory. WP seems to not interpret it well and I have to set up Alias directives in the virtualhost configuration to compensate. Are you doing anything similar with the app/ directory?

bretthopper 13y ago
It's being used in production for roots.io right now but it's still a work in progress. Seems like your issue has to do with your symlink setup. We don't need to do any special configuration with the web server. Here's the configuration that deals with app/: https://github.com/roots/bedrock/blob/master/config/application.php#L25-L27 https://github.com/roots/bedrock/blob/master/config/applicat...
pestaa 13y ago
I believe you're missing Options +FollowSymLinks from your Apache configuration and is not a problem with WP actually.

csomar 13y ago

Are you hiring freelancers/contractors?

bretthopper 13y ago
Roots isn't actually a "company". Just an open source organization although we do sell a few things like screencasts. If you're interested in work to do with WP/Roots you can check out this thread on our forum: http://discourse.roots.io/t/looking-for-work-post-your-info-here/743 http://discourse.roots.io/t/looking-for-work-post-your-info-...