bruandet

<h4>An xterm-like plugin to run non-interactive shell commands.</h4>
<p>WPTerm is an xterm-like plugin. It can be used to run non-interactive shell commands from the WordPress admin dashboard.</p>
<blockquote>
<p>Just like a terminal, WPTerm lets you do almost everything you want (e.g., changing file permissions, viewing network connections or current processes etc). That’s great, but if you aren’t familiar with Unix shell commands, you can also damage your blog. Therefore, each time you use WPTerm, please follow this rule of thumb: <strong>if you don’t know what you’re doing, don’t do it!</strong></p>
</blockquote>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/NHlWrEK6JfE?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h4>Compatibility</h4>
<p>WPTerm is not compatible with Microsoft Windows; it works on Unix-like servers only.</p>
<p>Because it makes use of PHP program execution functions such as <code>exec</code> or <code>shell_exec</code>, it may not be compatible with some shared hosts that have disabled these functions. To make sure your server is compatible, follow these steps:</p>
<ul>
<li>Download <a href="https://nintechnet.com/bruandet/wpterm-check.txt" title="" rel="nofollow ugc">this script</a>.</li>
<li>Rename it to “wpterm-check.php”.</li>
<li>Upload it inside your website root folder.</li>
<li>Go to http://YOUR WEBSITE/wpterm-check.php</li>
<li>Delete it afterwards.</li>
</ul>
<h4>Password Protection</h4>
<p>You can (and probably should!) password protect the access to WPTerm. Consult the contextual help, or type <code>help</code> at the terminal prompt to get more details about how to enable this feature.</p>
<h4>Features</h4>
<ul>
<li>Selectable PHP program execution function to run commands.</li>
<li>Custom fonts family, size and color.</li>
<li>Custom background color.</li>
<li>History and scrollback buffer.</li>
<li>Terminal bell (audible / visible).</li>
<li>Optional password protection.</li>
<li>Contextual help.</li>
<li>Multisite compatible (only accessible to the SuperAdmin).</li>
</ul>
<h4>Supported Languages</h4>
<ul>
<li>English</li>
<li>French</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 3.3+</li>
<li>PHP 5.3+</li>
<li>Unix-like OS (Linux, *BSD etc) only. WPTerm is <strong>NOT</strong> compatible with Microsoft Windows.</li>
</ul>


WPTerm

Ok maybe not 100 times a day, but I wouldn't be surprised if I was responsible for 75% of the active installs. I adore this plugin and use it multiple times a day. If it didn't exist I'd have to go build it!

I use this plugin 100 times a day

Thanks so much for developing this. Exactly what I needed.

Perfect!

Terrific plugin. I always forget the IPs and bash logins of my cloud machines. Saves time looking it up.

Great achievement for WordPress


Thank you for creating and maintaining this plugin, we find it very useful when debugging issues on customers websites.

Keep up the good work,
Alex

A very useful plugin

Perfect for testing and debugging cURL. 
Thanks a lot! 

Wonderful

An xterm-like plugin to run non-interactive shell commands.

rsprta

<p>Blog Terminal generates a terminal-like box that you can use to demonstrate terminal output or show the entry of terminal/console commands in a manner that is more demonstrative of actually using a Linux/Unix terminal or Windows cmd shell.</p>
<p>The code is a fork of Post Terminal, which is a fork of WP-Terminal which in turn is a modification of WP-Syntax, a source code highlighter plugin for WordPress.</p>
<p>Unlike Post terminal, it uses <code>[terminal]</code> shorthand for the terminal box. It also shows prompt only on lines explitly set to do that.</p>
<h4>Basic Usage</h4>
<p>The most basic usage is to wrap your terminal blocks with <code>[terminal][/terminal]</code> tags. If no further options are defined within the tag a generic prompt is generated using  ‘user@computer’ with no working directory shown. This is similar to exporting PS1=”\u@\h:$ ” in sh(1), setting prompt=”%n@%m:$ ” in csh(1), etc.<br />
Other options available within the tag are user=”user”, computer=”computer”, and  cwd=”/path/to/directory”. These allow you to override the generic user@computer settings as well as provide a ‘current working directory’.<br />
The prompt is only shown on the lines starting with ‘$ ‘. So you can mix commands with simulated terminal output.</p>
<h3>Usage</h3>
<p>Wrap terminal blocks with <code>[terminal user="username" computer="computername" cwd="/path/to/directory"]</code> and <code>[\terminal]</code>. They are all optional. “user” and “computer” will be shown if you don’t provide them, cwd is purely optional.</p>
<p><strong>Example 1: No customized command</strong></p>
<pre><code>[terminal]
$ ls -a
[/terminal]
</code></pre>
<p><strong>Example 2: User and computer customizations</strong></p>
<pre><code>[terminal user="tux" computer="linux"]
$ ls -a
[/terminal]
</code></pre>
<p><strong>Example 3: Customizing just the user</strong></p>
<pre><code>[terminal user="dak"]
$ ls -a
[/terminal]
</code></pre>
<p><strong>Example 4: Customizing user, computer and displaying a working directory</strong></p>
<pre><code>[terminal user="root" computer="linuxserver" cwd="/usr/src/linux"]
$ make mrproper
 ...
 ... 
[/terminal]
</code></pre>


Blog Terminal

Blog Terminal provides a terminal-like box for embedding terminal commands within pages or posts.

WPTerm vs Blog Terminal