-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible to redirect from apache to groovebasin? #495
Comments
This is reasonable. Should be pretty easy to fix. Let me take a look at it tonight. |
Very good. Please let me know if I can be of assistance. |
[Andrew Kelley]
Do you now have any idea how much work this will be to fix? Happy hacking |
Hi. Any news on getting a reverse proxy to work with groovebasin? I Happy hacking |
@petterreinholdtsen fwiw, reverse proxy works just fine, the problem is that groovebasin expects to live in |
[Felipe Sateler]
Right. Nope, it is not. :( I use pagekite on the host to make it Happy hacking |
Hi. Any news on making groovebasing "relocatable" URL-vise? Is it on your short term plan, or moved into the indefinite future? |
Hi. Did this prove impossible to fix, despite the comment from 2016-08-31 about it being pretty easy to fix? I would love to have use groovebasin via pagekite on my Freedombox, but for this to work URL must be relative to my Apache site. |
The groovebasin package in Debian was just orphaned, ie no one in Debian at the moment have time to maintain it. Freedombox is based on Debian. As this issue has been unsolved for two years, I suspect the chance of getting groovebasin into Freedombox was significantly reduced. :( |
I would like to run groovebasin on my Freedombox, where I use pagekite to forward the https port from apache to a publicly available IP address. For this to work with groovebasin, I would like to set up groovebasin behind apache. But I am unable to get this to work. I've tried using this content in /etc/apache2/conf-available/groovebasin.conf and running a2enconf groovebasin:
The problem is that groovebasin do not understand that all its URLs have changed, and ask the browser to load /app.css, /app.js and stuff under /vendor/. Is there a way to tell groovebasin what URL base to use when sending URLs to the browser?
The text was updated successfully, but these errors were encountered: