From 365ad263c5b3ec0ce56d0505dae694d981f8a3c2 Mon Sep 17 00:00:00 2001 From: Stef Walter Date: Fri, 14 Nov 2014 15:39:38 +0000 Subject: Fix plugin tutorial extract command --- content/cockpit/cockpit-plugin-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content') diff --git a/content/cockpit/cockpit-plugin-tutorial.md b/content/cockpit/cockpit-plugin-tutorial.md index 2fd0a76..b189a07 100644 --- a/content/cockpit/cockpit-plugin-tutorial.md +++ b/content/cockpit/cockpit-plugin-tutorial.md @@ -15,7 +15,7 @@ For example the *Terminal* that you see there is implemented as a tool. But lets So break out your terminal, lets make a package called *pinger* that checks whether your server has network connectivity to the Internet by pinging another host. Nothing too fancy. We'll just be spawning a process on the server to do the work. I've prepared it for you as [an example here](http://stef.thewalter.net/files/pinger.tgz), and we can look it over, and modify it. To download the example to your current directory: :::text - $ wget http://stef.thewalter.net/files/pinger.tgz -O - | tar -xf - + $ wget http://stef.thewalter.net/files/pinger.tgz -O - | tar -xzf - $ cd pinger/ Components, and more specifically their HTML and Javascript files, live in package directories. In the package directory there's also a `manifest.json` file which tells Cockpit about the package. The `pinger` directory above is such a package. It's `manifest.json` file looks like this: -- cgit v1.2.3