-
Notifications
You must be signed in to change notification settings - Fork 607
Closed
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers
Description
The CLI currently gets stuck on user prompts (e.g. unable to input a valid email address). Not sure if it's something as simple as a trailing new line, or more complicated.
Setup
- build the CLI for windows, e.g.
GOOS=windows GOARCH=amd64 CGO_ENABLED=0 go build -o cortex ./cli
- upload the CLI to a public bucket, e.g.
aws s3 cp cortex s3://cortex-cli-david/cortex.exe
- spin up an instance
a. use the "Microsoft Windows Server Base with Containers" AMI
b. at least a "large" instance type
c. at least 30gb storage
d. the security group must allow incoming RDP traffic on port 3389 - download Microsoft Remote Desktop 10 from the mac app store
- once the instance is running, in the EC2 console, click Actions > Connect, then download the remote desktop file, and get the password (by uploading the
.pem
file for the key used to spin up the instance) - open the rdp file by double-clicking from Finder, and paste the password to log in
- click the search icon, type "cmd" and click "Command Prompt"
- check docker is running with
docker ps
(there just be no errors) - set telemetry endpoints
a.SET CORTEX_TELEMETRY_SENTRY_DSN=https://***@sentry.io/***
b.SET CORTEX_TELEMETRY_SEGMENT_WRITE_KEY=***
- download the CLI, e.g.
curl https://cortex-cli-david.s3-us-west-2.amazonaws.com/cortex.exe --output cortex.exe
- run
cortex.exe -h
to check that the CLI runs - run
cortex.exe cluster up
to spin up a cluster
Old cmd.exe notes
md .cortex
echo telemetry: false > .cortex/cli.yaml
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers