Running Hydra without RethinkDB

99 views
Skip to first unread message

Jan Olszak

unread,
May 30, 2016, 4:00:39 PM5/30/16
to ory-hydra
Hi,
Is it possible to run hydra without Rethinkdb, just some in-memory storage? Just for development purposes.

Starting this https://github.com/ory-am/hydra/blob/master/docker-compose.yml crashes my OS after some time. 
(8GB, i7, Ubuntu 14.04).

Hail Hydra,
Jan

Aeneas Rekkas

unread,
May 30, 2016, 4:26:17 PM5/30/16
to ory-...@googlegroups.com

Yes, just do `go run main.go` that will start hydra without database or remove the DATABASE_URL in docker-compose.yml

--
You received this message because you are subscribed to the Google Groups "ory-hydra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ory-hydra+...@googlegroups.com.
To post to this group, send email to ory-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ory-hydra/0b43b33a-81cd-4bb7-a7a5-f97dfbe9e03f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jan Olszak

unread,
May 30, 2016, 5:03:20 PM5/30/16
to ory-hydra
When I remove DATABASE_URL Hydra still tries to connect to the database couple of times and then it exits 1.

Here's the modified docker-compose.yml

version: '2'

services:

  hydra:
    build:
      context: .
      dockerfile: Dockerfile-dangerous
    volumes:
      - hydravolume:/root
    ports:
      - "4444:4444"
    environment:
      - SYSTEM_SECRET=${SYSTEM_SECRET}
      - CONSENT_URL=http://${DOCKER_IP}:3000

  consent:
    environment:
      - HYDRA_URL=https://hydra:4444
      - NODE_TLS_REJECT_UNAUTHORIZED=0
    image: oryam/hydra-idp-react
    links:
      - hydra
    volumes:
      - hydravolume:/root
    ports:
      - "3000:3000"

volumes:
  hydravolume:
    driver: local

Aeneas Rekkas

unread,
May 30, 2016, 5:07:44 PM5/30/16
to ory-...@googlegroups.com

ah it might be possible that the database URL was saved to `/root/.hydra.yml`. try deleting the volume using `docker volume ls` `docker volume rm <id>` (should be something like hydra_hydravolume). make sure that you run `docker-compose kill` before.

alternatively run `docker-compose kill && docker-compose rm -f && docker-compose up`

hope that helps

Jan Olszak

unread,
May 30, 2016, 6:19:54 PM5/30/16
to ory-hydra
It works now, thanks. I got used to data containers and forgot to cleanup volumes.

There's a mistake in the Linux example in README.md:  DOCKER_IP=tutorialpassword. Maybe it's not needed at all.
Also the example SYSTEM_SECRET is quite long for just an example.

Cheers!

Aeneas Rekkas

unread,
May 31, 2016, 3:59:28 AM5/31/16
to ory-...@googlegroups.com

I might have to fix what get's written in they .hydra.yml file.

Right now the system secret must be > 32 byte in order for AES to be 256bit strong. I will change that however to sha265(password)[:32] so passwords can be shorter

Reply all
Reply to author
Forward
0 new messages