I created a new page and menu item called Drupal Distributions and listed all of the platforms that I have installed locally on my Aegir instance (i.e., hostmaster). It takes about 60 seconds to install a new website and then its on to configuration. I downloaded tar files into the platform directory for these distributions but am in the process of finding and creating make files for unique Drupal sites. In fact, that is all I need to do from now on. Drush Rules in this environment, I can implement any drush commands to any site via drush aliases.
basic lesson
- Drupal is not an end in itself
- Drupal is part of a larger conception, and the larger conception is as a tool for selling a product
- Drupal is a tool for creating an eficient and error-free interface for my client to add content about their product
- i am here to serve the client - this is part of becoming a professional
- Drupal is rarely the most important part of the package
- what the client is selling is the most important part of the package by far
- next comes the combination of information architecture, SEO and imagery - since the internet is primarily a visual and interconnected medium
- then there is Drupal - it is in a supporting role
- no matter how important Drupal is or isn't - i have to approach using Drupal to create an efficient and error-free interface as if it is the most important part of the process
- as a consultant, i make money based on completed Drupal products
- and i need to complete as many Drupal projects per month as i can
I am pretty impressed with the active members of the Drupal community. How they work, love, play and enhance Drupal is a lot of effort. I am just starting out as a Drupal consultant and I am just barely treading water. I have so much work to do it is incredible. There are so many sites out there with Drupal madness (i.e., a beginner set them up without much forethought) that it will take a few years to get everyone back in shape, caught up and willing to still be a part of this Drupal revolution. I had even thought about calling my company "Drupal Rescue". hahaha
By Carlye Adler August 30, 2011 | 12:30 pm | Wired September 2011
Everything you know about starting a company is wrong. At least that’s what Eric Ries says. The former entrepreneur has developed a counterintuitive strategy he calls the Lean Startup. The philosophy has been endorsed by Silicon Valley royalty like Tim O’Reilly, Marc Andreessen, and Mitch Kapor. It’s all explained in his new book, Lean Startup, but we still had a few questions.
Some key advantages:
- Pushing remote changes automatically updates the live site
- Server-based site edits won’t break history
- Simple, no special commit rules or requirements
- Works with existing sites, no need to redeploy or move files
Overview
The key idea in this system is that the web site exists on the server as a pair of repositories; a bare repository alongside a conventional repository containing the live site. Two simple Git hooks link the pair, automatically pushing and pulling changes between them.
cache_form is "state" cache | cache_block is menus and menu paths | cache_page is only anonymous users
A. opcode cache - APC
B. object cache | memcache | moves db cache to sys RAM
bins are instances of cache
Types of caching available:
Boost is a "static cache" file - HTML
"Reverse Proxy" - NGINX, Varnish, Squid, Pressflow
Reverse Proxy happens before the page is being cached
Boost - happens during early page cache
object cache - db cache(normal caching) - happens during late page cache
Audience: Developers and coders, Site administrators
Page status: Incomplete
Last modified: July 19, 2010
Important: This document has been updated to reflect changes recently added to drush-HEAD that will become part of drush-3.0-beta2. At the time of this writing, the most recent drush tag is drush-3.0-beta1, which contains a different implementation of the site alias feature.
Date: Fri, 18 Feb 2011 10:14:56 +0000
From: Andy Fowlston
Subject: [development] Workflow: staging server, source control, and
the files directory
To: "development@drupal.org"
Message-ID:
Content-Type: text/plain; charset="us-ascii"
Hi all,
I have a question about people's practices using a staging server and source control. I'm keen for us to have a sensible workflow while developing sites, and currently we have the following setup.
