Skip to content
This repository was archived by the owner on Apr 23, 2018. It is now read-only.

place dudle directly into webroot#2

Open
sonntagd wants to merge 1 commit intofonk:masterfrom
sonntagd:feature/dudle_in_documentroot
Open

place dudle directly into webroot#2
sonntagd wants to merge 1 commit intofonk:masterfrom
sonntagd:feature/dudle_in_documentroot

Conversation

@sonntagd
Copy link
Copy Markdown

Hi, I made a little change to the VirtualHost config file. Now the dudle application lives directly in the webroot. To me, this is more natural as I access the app on a separate subdomain. Before the change, I would get an Apache information page in the webroot.

@fonk
Copy link
Copy Markdown
Owner

fonk commented Jun 25, 2016

Hi Dominic!

If you use haproxy to distribute the requests to different docker containers for differnet URLs, it makes the configuration much more simple, if you don't have to rewrite the URLs... Maybe it would be the best way to make the URL configurable via docker environment variables - what do you think?

Best regards,
Frank

@sonntagd
Copy link
Copy Markdown
Author

sonntagd commented Jun 25, 2016

I'm using an nginx-proxy in front of the dudle (and other) docker container(s). Your suggestion, to make the URL configurable, would be the most flexible way!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants