[alpha.19] 'ghost ls' not showing proper status

[PaszaVonPomiot]

Issue Summary

'ghost ls' command does not show my production instance running. It works okay for development.

Steps to Reproduce

1. Install alpha.19 and setup for both production and development
2. ghost start
3. ghost ls

Technical details:

Ghost Version: alpha.19
ghost-cli Version: 1.0.0-alpha.16
Node Version: v6.10.0
OS: Debian 3.16.39-1+deb8u1
Database: MariaDB 10.0.29 & SQLite3

Log

ghost@ghost:/var/www/ghost$ ghost start
 ✔ Validating config
✔ Starting Ghost
You can access your blog at http://192.168.1.75:2368/
ghost@ghost:/var/www/ghost$ ghost ls
┌──────────────┬────────────────┬─────────┬─────┬──────┬─────────────────┐
│ Name         │ Location       │ Status  │ Url │ Port │ Process Manager │
├──────────────┼────────────────┼─────────┼─────┼──────┼─────────────────┤
│ 192.168.1.75 │ /var/www/ghost │ stopped │ n/a │ n/a  │ n/a             │
├──────────────┼────────────────┼─────────┼─────┼──────┼─────────────────┤
│ ghost-local  │ /var/www/ghost │ stopped │ n/a │ n/a  │ n/a             │
└──────────────┴────────────────┴─────────┴─────┴──────┴─────────────────┘

ghost@ghost:/var/www/ghost$ ghost stop
✔ Stopping Ghost
ghost@ghost:/var/www/ghost$ ghost -D start
 ✔ Validating config
✔ Starting Ghost
You can access your blog at http://192.168.1.75:2367/
ghost@ghost:/var/www/ghost$ ghost ls
┌──────────────┬────────────────┬───────────────────────┬───────────────────────────┬──────┬─────────────────┐
│ Name         │ Location       │ Status                │ Url                       │ Port │ Process Manager │
├──────────────┼────────────────┼───────────────────────┼───────────────────────────┼──────┼─────────────────┤
│ 192.168.1.75 │ /var/www/ghost │ stopped               │ n/a                       │ n/a  │ n/a             │
├──────────────┼────────────────┼───────────────────────┼───────────────────────────┼──────┼─────────────────┤
│ ghost-local  │ /var/www/ghost │ running (development) │ http://192.168.1.75:2367/ │ 2367 │ local           │
└──────────────┴────────────────┴───────────────────────┴───────────────────────────┴──────┴─────────────────┘

ghost@ghost:/var/www/ghost$ cat ~/.ghost/config
{
  "instances": {
    "192.168.1.75": {
      "cwd": "/var/www/ghost"
    },
    "ghost-local": {
      "cwd": "/var/www/ghost"
    }
  }
}

ghost@ghost:/var/www/ghost$ cat config.production.json
{
  "url": "http://192.168.1.75:2368/",
  "pname": "192.168.1.75",
  "server": {
    "host": "192.168.1.75",
    "port": 2368
  },
  "process": "systemd",
  "database": {
    "client": "mysql",
    "connection": {
      "host": "localhost",
      "user": "root",
      "password": "*******",
      "database": "ghost_prd"
    }
  },
  "logging": {
    "transports": [
      "file",
      "stdout"
    ]
  },
  "auth": {
    "type": "password"
  }
}

ghost@ghost:/var/www/ghost$ cat config.development.json
{
  "url": "http://192.168.1.75:2367/",
  "pname": "ghost-local",
  "server": {
    "host": "192.168.1.75",
    "port": 2367
  },
  "process": "local",
  "database": {
    "client": "sqlite3",
    "connection": {
      "filename": "/var/www/ghost/content/data/ghost-local.db"
    }
  },
  "logging": {
    "transports": [
      "file",
      "stdout"
    ]
  }
}

[ErisDS]

I was able to reproduce this today.

[acburdine]

Ok, so I figured out what this is. Because we use the get method from lodash in a lot of places, the dots in the IP address that shows up are being treated as a property access chain.

I'll add a sanitization method for the process name that will convert the dots to dashes to make sure this doesn't happen.