Logout in Linux shell command prompt without leaving your commands history

When we logout in Linux shell command prompt, we leave all the commands we have executed in Bash history file. For some reason you don't want your activity to be traced, the following is a command that will prevent your history of commands to be saved:

  
kill -9 $$
  

Just in case this command is hard to remember, it is useful to make this command available for easy access by using up/down arrow keys . Edit your Bash history file:

  
vi ~/.bash_history
  

… and enter:

Tags

Drush can't connect to MySQL server on localhost using WinNMP on Windows

First time I setup and test Drush on my local machine using WinNMP on Windows executing a cache clear on a local Drupal site under Git BASH or cygwin:

  
drush @webfoobar cache-rebuild
  

... I get this error:

  
No Drupal site found, only 'drush' cache was cleared
  

I excuted the following drush command to investigate the cause of the error:

  
drush @webfoobar -d st
  

... got the following output message:

Solution to "The filename, directory name, or volume label syntax is incorrect." error in Drush custom PHP path

It is possible to assign a specific PHP version to execute Drush commands for special Drupal site via Drush aliases configuration file. However in Windows, we can get error:

  
The filename, directory name, or volume label syntax is incorrect.
  

… if the we follow the Windows syntax path.

This error is printed from C:\composer\vendor\drush\drush\includes\exec.inc

Tags

How to use your custom php.ini in Drush

The following codes shows how can we tell Drush to use our custom php.ini:

  
$aliases['wf'] = array (
  'uri' => 'http://d8webfoobar.loc',
  'root' => 'C:/WinNMP/WWW/drupal',
  'php' => 'C:/WinNMP/bin/PHP/64bit-php-7.2/php.exe',
  'php-options' => '--php-ini=C:/WinNMP/conf',
);
  

To test, execute the following command:

  
drush @wf status
  

The screenshot is the output of the command above showing that the custom php.ini is already recognized by Drush:

Tags

Synergy server and client wont connect

Synergy is a software that shares a mouse and a keyboard between many computers. Setting this up requires the computer that shares the mouse and keyboard configured as server and the rest of the computers that are being controlled will be the clients. The ussual challenge in setting this up is making the server and client(s) get connected. One feature of Synergy is the option to use SSL encryption connection. And the common mistake is that the server configured to use SSL encryption connection and the client(s) is(are) not and the following are the logs that will show on server: