Top Nav

Clearing PHP opcache

Great article on how to clear the PHP opcache:

To facilitate use on a Plesk server created script and mapped into namespace:

Here’s the script:

And here’s the Apache config to map into a virtual host:

This above config should be placed in the “Apache & nginx setting” screen in the “Additional directives for https” field. In addition to setting the alias path we’re also setting the PHP handler.

Additionally under “Password protected directories” added password protection for “/opcache_clear”. This is just a placeholder for the password file which is referenced in the above config.


Bash Directory Stack

Ryan at Level1Techs introduces the Bash Directory Stack:

Quick Reference

The Bash Directory Stack is FILO (First In, Last Out)

pushd /some/dir/path

  • push pwd to stack and change to new directory


  • list stack

dirs -V

  • list stack vertical with index


  • change directory to directory at position 1 in stack

pushd +n

  • change directory to “n” indexed directory
  • actually a rotate
  • also accepts “-n”

popd +n

  • remove indexed item from stack
  • also accepts “-n”

dirs -c

  • clear stack

Block On X-Forwarded-For

Block an IP address based on the X-Forwarded-For header:




“find” Newer Files & Sort By Date

Sort “find” results by date:

Find files newer then a specific file:

And combined:




Apply Basic Auth To Site With Excluded Virtual Path Under Plesk With Apache 2.4

We want to password protect a WordPress development site but allow unauthenticated access to the wp-json/ path. Hosting platform is Plesk with Apache 2.4. We’ll assume the domain is “” and the assigned IP is “w.x.y.z”.

There are probably better ways to accomplish the goal but this approach seems to work.

Step 1. – In Plesk add a Protected Directory named “/donotremove” and add appropriate user/passwords.

Step 2. – In Plesk on the “Apache & nginx Setting” screen under “Additional nginx directives” add the following:

Step 3. – In Plesk on the “Apache & nginx Setting” screen under “Additional directives for HTTP” and “Additional directives for HTTPS” add the following: