You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Managing multiple Github projects with multiple deploy keys on a single server
Managing multiple Github projects with multiple deploy keys on a single server
I have a number of projects on a single server that all have their own git repos on Github. My problem is that I need to create a separate deploy key for each one of these but I have to keep adding and re-adding the ssh-keys when I am doing deployments, ex:
eval"$(ssh-agent -s)"
ssh-add id_site1
I figured that there had to be a way to simplify this using SSH config but ended up with something like this which did not work, it always assumed the first entry in the list.
Beyond module security updates: How to craft a holistic security strategy
This past year, Drupal site maintainers raced to patch their sites to address back-to-back critical security issues in Drupal 7/8, with exploits being detected in the wild within hours after the patches were released. These updates, while not out of the ordinary for open source software, occurred in an an increasingly complex security environment that is seeing a greater range of hostile actors executing more sophisticated, targeted, and damaging website attacks.
As a site owner, how worried should I be about these threats? What can I do besides keeping my modules patched? Are there other best practices for protecting my site from common attacks? How can I approach web security more holistically?
In this session, we will introduce a framework for understanding Drupal website security and how to assess possible solutions. This will include:
TIL: Checking module schema in database to confirm whether module updates have run
TIL: How to check module schema in database to confirm whether module updates have run
If I’m running database updates on a Drupal site and there is some question about whether or not the update fired, I can check this in the database itself from the command line.
Every module that has database updates will define these in their install file, ex. ctools.install and that file will have a number of install hooks that reference the schema number, ex:
/** * Revert the length of the ctools_object_cache.name column back to 128. */
I'm often running a single query that produces a set of results that I would like to export into a CSV.
For example, in a query against the url_alias table, I will want to grab the following and have it export into a spreadsheet rather than
mysql> SELECT source,alias FROM url_alias WHERE alias LIKE "library%";
+-----------+----------------------------------------------------------------+
| source | alias |
+-----------+----------------------------------------------------------------+
Drupal 8.x Search API processor plugin for boosting search items by term reference field
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Drupal 7: Create menu_hook to load random node of approved content types for more efficient debugging and testing
Drupal 7: Create menu_hook to load random node by type
On many projects, I often have a need to be able to see a random node of a particular content type for debugging or load testing. I use this function on Drupal 7 sites in my core module / feature to add a hook of:
(I use this instead of a view sorted by random because I want to be redirected to the full path of the node.)
Leaving off the content-type will use a random type from the array of valid content types I have provided. Providing an invalid content type will redirect it to an item from my core (or default) content-type.