anvilresearch / connect

A modern authorization server built to authenticate your users and protect your APIs
http://anvil.io
MIT License
361 stars 85 forks source link

Getting connect up and running on OS X #294

Closed AlexZeitler closed 8 years ago

AlexZeitler commented 8 years ago

Hi,

I tried to get connect up and running on OS X and Node.js 0.12.7

What I did:

npm install -g anvil-connect-cli
mkdir hello-connect
cd hello-connect
nvl init
? What would you like to name your Connect instance? hello-connect
? What (sub)domain will you use? localhost
? Would you like to use Docker? No
? Would you like to run Redis? No
? Would you like to run nginx? No
   create git repository
   create connect/keys/sig.rsa.pub.pem
   create connect/keys/sig.rsa.prv.pem
   create connect/keys/enc.rsa.pub.pem
   create connect/keys/enc.rsa.prv.pem
   create connect/keys/setup.token
   create .gitignore
   create connect/server.js
   create connect/config/development.json
   create connect/config/production.json
   create connect/package.json
   create connect/.bowerrc
   create connect/bower.json
Connect all the things :)
cd connect
npm install
bower install
node server.js
Starting 8 workers
Anvil Connect pid 16074 is running on port 3000
Anvil Connect pid 16072 is running on port 3000
Anvil Connect pid 16070 is running on port 3000
Anvil Connect pid 16071 is running on port 3000
Anvil Connect pid 16076 is running on port 3000
Anvil Connect pid 16075 is running on port 3000
Anvil Connect pid 16069 is running on port 3000
Anvil Connect pid 16073 is running on port 3000

Go to Chrome, open http://localhost:3000

{
Anvil Connect: "Welcome",
issuer: "http://localhost:3000",
version: "0.1.58"
}
nvl setup http://localhost:3000 --token-file ~/src/hello-connect/connect/keys/setup.token
Warning: you are communicating over plain text.
http://localhost:3000 does not point to an Anvil Connect server

How can I connect with the setup without SSL?

(I also tried to use nginx and create a self signed cert but I could only connect to localhost:3000 but not use https://localhost or https://localhost:3000)

adalinesimonian commented 8 years ago

Are you running Redis?

AlexZeitler commented 8 years ago

Redis did not run. After spinning up a redis instance, I have been able to run the setup. Thanks :+1: