3 ms·
90 mins. What is your secret? Because I can't get one up in 90 minutes even starting with the theme pre-written and automating the deployment as much as I can
by patio11 17y ago
90 mins.
What is your secret? Because I can't get one up in 90 minutes even starting with the theme pre-written and automating the deployment as much as I can -- the amount of manual settings for plugins, sidebar widgets, and the like always eats my time.
- ryanwaggoner 17y agoThese are for clients who typically only use a couple plugins, usually Akismet and a contact form. So other than the theme stuff, which probably takes about an hour, I'm usually just installing WP, which takes about 3 mins (they're usually using a host that has one-click installation), then I upload the plugins that I use on everything and enable them, which takes another 2-3 mins, then I configure things, which usually means turning on permalinks, changing admin password, and setting up the contact form. Create a "contact us" page, edit the about us page, and I'm pretty much done. The non-theme stuff takes about 30 mins. But these are sites for authors, many of which are new to the idea of blogging, so a lot of complicated plugins and widgets to deal with is too much for them.
- thesethings 17y agoYou're not alone. It's not for lack of options, but like many parts of Drupal, the automated install process hasn't "stayed still" for more than a version for the best practices to really evolve. The most famous way is something called Install Profile. The definition and underpinnings of this module have changed drastically from version to version, and it is not that well documented. A more recent entrant is a system called Aegir which is a set of multiple modules. There is also a Drupal shell called Drush that can automate some things, but obviously it itself needs to be present and installed to be utilitzed :D. Myself? I've written an ugly bash script that basically downloads and moves all the modules into place, and talks to mysql to enable them. I would never advise anybody else to use this method, or at least not use my script ;D In a recent Lullabot podcast (probably the most well-known, and definitely most helpful Drupal-based business I know of), they referred to a database-centric way of automating installs that sounded like it could also be just a db script. They promised a blog post, which I am eagerly anticipating. Anyway, your main point about Drupal setup being cumbersome, is true. Most people whose work is all Drupal have ways to deal with this, but if Drupal is only a small part of your computing life, it's not obvious what the best practice is.