		@@ -10,2 +10,3 @@ #!/usr/bin/env node
		const fs = require('fs');
		const path = require('path');
		const optionDefinitions = require('./lib/options');
		@@ -17,3 +18,10 @@ const usage = require('./lib/usage');
		const hawkinitWizzard = (save, timeout) => {
		// clear the screen
		console.log('\x1B[2J');

		// show the ascii logo
		const logo = fs.readFileSync(path.join(__dirname, 'logo'), 'utf8');
		console.log(logo);

		// .. and the ascii label
		process.stdout.write(
		@@ -20,0 +28,0 @@ chalk.blue(

lib/engine.js

		@@ -95,3 +95,3 @@
		}
		fs.writeFileSync(`${directory}/docker-compose.yaml`, result);
		fs.writeFileSync(`${directory}/docker-compose.yml`, result);
		setTimeout(() => {
		@@ -133,3 +133,3 @@ status.stop();

		console.log(chalk.grey('Adding the template or WildFly servers with agent installed.'));
		console.log(chalk.grey('Adding the template with WildFly servers with agent installed.'));
		// the image stream doesn't expect the fully qualified image including the tag
		@@ -136,0 +136,0 @@ // const hawkflyImg = `pilhuhn/hawkfly:${answers.wfStandaloneVersion}`;

package.json

		{
		"name": "hawkinit",
		"version": "1.5.5",
		"version": "1.5.6",
		"description": "This CLI tool sets up the Hawkular Services together with couple of servers to monitor.",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -81,3 +81,3 @@ # Hawkinit

		If you navigate to `/tmp/tmp-11573k3ujXFLACh9z`, you can run `docker-dompose up` to start it again. This is not a standard use-case, though. Any other `docker-compose` command works just fine. So for instance you may want to see only the Cassandra logs by `docker-compose logs -f myCassandra` or inspecting the Hawkular Services container by `docker-compose exec hawkular /bin/bash`, etc. Also, nothing protects you from editing the `docker-compose.yaml` file that was created in that tmp directory.
		If you navigate to `/tmp/tmp-11573k3ujXFLACh9z`, you can run `docker-dompose up` to start it again. This is not a standard use-case, though. Any other `docker-compose` command works just fine. So for instance you may want to see only the Cassandra logs by `docker-compose logs -f myCassandra` or inspecting the Hawkular Services container by `docker-compose exec hawkular /bin/bash`, etc. Also, nothing protects you from editing the `docker-compose.yml` file that was created in that tmp directory.

hawkinit - npm Package Compare versions

New alerts