Closed sgama closed 5 years ago
The config file gets saved on shutdown, but if a simple reload already makes all configured bees disappear, it sounds like a different issue. Can you reproduce this by directly running the image (like mentioned in the README) outside docker-compose?
Interesting! I figured it out.
I ran the image directly as mentioned in the README:
docker run --name beehive -d -e CANONICAL_URL="http://localhost:8181" -p 8181:8181 fribbledom/beehive
and it worked. I was able to save and retrieve a bee. So I was confused as docker-compose is just a wrapper around docker. So I created a new Dockerfile from scratch and it also worked!
Turns out it was the trailing slash in the CANONICAL_URL
. Using
environment:
- CANONICAL_URL=http://localhost:8181
in the docker-compose file pasted above worked.
You can't have a trailing slash.
Interesting find! I need to look into what's causing that and make sure that's not leading to any issues. It's probably a fairly common "mistake" (I wouldn't even call it one, it's perfectly valid input).
Fixed in master. Thanks for the detailed report!
I'm trying to set up Beehive on my server but I can't seem to get it to save the Cron or Twitter bee. Here's my docker-compose file:
The docker logs don't seem to show any error. Process to reproduce:
No bees are available. Checking /conf/beehive.conf shows a JSON file with these contents:
Let me know if I can provide any additional clarifications or if you require any help with the docker-compose file.