Skip to content
This repository has been archived by the owner on Nov 8, 2019. It is now read-only.

Commit

Permalink
Merge pull request #22 from ingrammicro/feature/change-default-path
Browse files Browse the repository at this point in the history
Update of default path for IMCO cli
  • Loading branch information
Javier Perez-Griffo authored Feb 8, 2018
2 parents e857b5e + 245cc9e commit f28a682
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 11 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Extract the contents with your zip compressor of choice and continue using the s

## Linux and OSX
### Configuration
Concerto configuration will usually be located in your personal folder under `.concerto`. If you are using root, concerto will look for contiguration files under `/etc/concerto`.
Concerto configuration will usually be located in your personal folder under `.concerto`. If you are using root, concerto will look for contiguration files under `/etc/imco`.
We will assume that you are not root, so create the folder and drop the certificates to this location:
```
$ mkdir -p ~/.concerto/ssl/
Expand Down Expand Up @@ -181,7 +181,7 @@ If you got an error executing concerto CLI:
- check that your internet connection can reach clients.concerto.io
- make sure that your firewall lets you access to https://clients.concerto.io:886
- check that client.xml is pointing to the correct certificates location
- if concerto executes but only shows server commands, you are probably trying to use concerto from a commissioned server, and the configuration is being read from `/etc/concerto`. If that's the case, you should leave concerto configuration untouched so that server commands are available for our remote management.
- if concerto executes but only shows server commands, you are probably trying to use concerto from a commissioned server, and the configuration is being read from `/etc/imco`. If that's the case, you should leave concerto configuration untouched so that server commands are available for our remote management.


# Usage
Expand Down
18 changes: 9 additions & 9 deletions utils/config.go
Original file line number Diff line number Diff line change
Expand Up @@ -20,18 +20,18 @@ import (
"github.com/mitchellh/go-homedir"
)

const windowsServerConfigFile = "c:\\concerto\\client.xml"
const nixServerConfigFile = "/etc/concerto/client.xml"
const windowsServerConfigFile = "c:\\imco\\client.xml"
const nixServerConfigFile = "/etc/imco/client.xml"
const defaultConcertoEndpoint = "https://clients.concerto.io:886/"

const windowsServerLogFilePath = "c:\\concerto\\log\\concerto-client.log"
const windowsServerCaCertPath = "c:\\concerto\\client_ssl\\ca_cert.pem"
const windowsServerCertPath = "c:\\concerto\\client_ssl\\cert.pem"
const windowsServerKeyPath = "c:\\concerto\\client_ssl\\private\\key.pem"
const windowsServerLogFilePath = "c:\\imco\\log\\concerto-client.log"
const windowsServerCaCertPath = "c:\\imco\\client_ssl\\ca_cert.pem"
const windowsServerCertPath = "c:\\imco\\client_ssl\\cert.pem"
const windowsServerKeyPath = "c:\\imco\\client_ssl\\private\\key.pem"
const nixServerLogFilePath = "/var/log/concerto-client.log"
const nixServerCaCertPath = "/etc/concerto/client_ssl/ca_cert.pem"
const nixServerCertPath = "/etc/concerto/client_ssl/cert.pem"
const nixServerKeyPath = "/etc/concerto/client_ssl/private/key.pem"
const nixServerCaCertPath = "/etc/imco/client_ssl/ca_cert.pem"
const nixServerCertPath = "/etc/imco/client_ssl/cert.pem"
const nixServerKeyPath = "/etc/imco/client_ssl/private/key.pem"

// Config stores configuration file contents
type Config struct {
Expand Down

0 comments on commit f28a682

Please sign in to comment.