Front & back web development by Electronic Press.
View the site and here.
Creating and manipulating content (entities) has become much less complex with EntityAPI in Drupal 7.
There are lots of examples out there for manipulating nodes, creating custom entity types, etc. Here's a quick one for programatically creating a comment entity and attaching it to a node.
Somehow, I've never came across vhost_alias_module until now.
If you're like us and have dev/stage/prod environments where one of the only httpd conf changes is the (sub)domain, writing a VirtualHost directive 3+ times can become a pain.
Enter vhost_alias_module, a super simple solution to this problem.
Now that we've got our server instance up and running with CentOS 6.5 (RHEL 6), there's a few things to check on before proceeding.
Configure & Update
As a first step, after logging in, lets update the server packages with
$ yum update -y. Next, change your root password with
There are lots of other things you should be doing at this point which will be covered in the Security section of this series. This includes things like:
Although being removed from core in D8, the book module can come in handy in some situations.
However, there's rather limited functionality in terms of menu organization. Particularly not being able to have "non-linked" headers for sections of the book.
Pivot is a multi-functional tablet stand that serves a variety of consumer needs including remote video conferencing, as well as a built-in entertainment system. Your smart device just got a little smarter.
Check out the site here!
Along with git, drush ― [Dru]pal [Sh]ell ― aliases are an extremely useful, and powerful tool when dealing with a drupal dev-stage-production workflow.
The idea is simple: create an alias for your different environments, allowing you to perform drush tasks on remote servers. Included is additional functionality such as syncing files, databases, or using any other drush command - even the usual
drush cc all et al.
Shared? VPS? Dedicated? Colocation? Cloud?
The first step in our PWS is an important one: choosing the type of hosting and a provider. There is no one correct answer, and everyone has their own opinions & requirements.
To start, the idea of shared hosting is nice. Set it up, forget about it. No sysadmin / devops. Sure, Pantheon is geared towards Drupal, and it's a great service. But not a lot of clients are willing to pay $400+/month for hosting one site. Finally, later in this series we'll be discussing a lot of additional packages not usable with shared hosting.
Azahar Coffee, a unique company that specializes in bringing coffee directly from the farm to the consumer. Their coffee is truly unique (yes, we've had it!) and they needed a website to match.
This series will aim to become a reference to creating an ideal Production Webserver. It is geared towards Drupal configurations, but can be used for any server whose main function is to serve webpages.
Creating a performant, secure, scalable, redundant, production server environment can be (is) a complicated task. Having managed dozens of servers for many years, by no means is this the only way to go. But if you're administering your own server with a lot of clients, this is what works for us.