I really wish Wordpress would ditch the shared-hosting first deployment model and grow up a bit. Thankfully https://roots.io/bedrock/ exists to bridge the gap if you're absolutely forced to use WP. - Source: Hacker News / 9 months ago
There are ready-made boilerplates like Bedrock and Sword but, at an architectural level, I'm not a fan of any I've seen. Source: 10 months ago
Is this any good? https://roots.io/bedrock/ for a plugin? Source: 10 months ago
As I only really use it for keeping stuff up to date, I'm looking at using Roots Bedrock for my next project. I'll then be keeping everything up to date via composer. Source: about 1 year ago
What advantages does WordPlate have over Bedrock[1], some of whose packages WordPlate also uses? [1] https://roots.io/bedrock/. - Source: Hacker News / about 1 year ago
Probably looking for a https://roots.io/bedrock/. Source: about 1 year ago
WordPress on containers is a very different beast if you actually want to use any of the advantages of containers. You probably need to figure out how to run upgrades by building a new image and not with the WP installer (which you need to disable to not have sudden version rollbacks). You probably want your plugins managed by compose and not a user. You probably want an S3 plugin for media. In fact, you probably... Source: about 1 year ago
I'd strongly advice using Bedrock ( https://roots.io/bedrock/ ) and possibly even Sage. Source: over 1 year ago
No, as far as I know it’s not that easy to accomplish with WordPress. You can use Bedrock (https://roots.io/bedrock/ ) as a Boilerplate for your development process. The Database can not be cloned to each environment that easily. Because every instance is working on it’s own. So if others want to work on their local machine they need a database dump which they have to setup manually on their machine. The only way... Source: over 1 year ago
So, what Sword really is and what problems does it solve? If you've heard of Bedrock, it's similar but with Symfony. Sword is Symfony running WordPress. - Source: dev.to / over 1 year ago
If it’s a big site, your best bet overall is to keep as much as possible in code: custom field definitions, CPT registration, form fields. Set settings using filters. Etc etc. If you use https://roots.io/bedrock/ then WP plugins can be defined in code (composer.json). Then the rule is to simply make database changes (content etc) on production and only ever sync from prod to staging. Source: over 1 year ago
Alternative approaches such as Bedrock offers more protection to these creds. The framework leverages ENV vars to store information and provides a convenient way to override configurations according to the environment. - Source: dev.to / over 1 year ago
The last months I spent researching robust and professional WordPress development workflows. In my mind, that always meant git, composer, deploy pipelines, continous integration etc. See e.g. bedrock. - Source: dev.to / about 2 years ago
[1] https://roots.io/bedrock/ [2] https://github.com/pantheon-systems/example-wordpress-composer. Source: about 2 years ago
Maybe have a look at Bedrock; https://roots.io/bedrock/ it's already set up for git as well as a few other nice things like composer and bcrypt. Source: about 2 years ago
i've used bedrock before, which does what youre asking for: https://roots.io/bedrock/. Source: about 2 years ago
If you professionally build a WordPress site, please consider turning off the native plugin and theme management, and replace it with composer and files non-writable to PHP. https://roots.io/bedrock/ is a neat boilerplate for how this can be done. - Source: Hacker News / over 2 years ago
Take a look at using Bedrock and Trellis if you're interested in using git and Composer to manage your WP install, along with having a Capistrano-like deployment system with zero-downtime. Source: over 2 years ago
I avoid it as far as possible. There are far, far better CMS's that are a better fit for a modern developer's workflow - I particularly like Statamic. When I do have to work with Wordpress, I generally use Bedrock since it means I can use Composer to manage plugins and themes as dependencies, and can more easily work with it locally, as well as being more secure out of the box. Source: over 2 years ago
You should take a look at Bedrock for WP: Https://roots.io/bedrock/. Source: over 2 years ago
Use version control to store all of your code changes, such as Github. You can also use a framework like Bedrock (https://roots.io/bedrock/) which will let you pull in Wordpress core as well as plugins via composer, rather than having each instance pull plugins in willy-nilly. Source: over 2 years ago
Do you know an article comparing Bedrock to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Bedrock. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.