-
Notifications
You must be signed in to change notification settings - Fork 60
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
STORAGE_URL
is not used globally: local.appspot.com
is still hardcoded somewhere
#162
Comments
STORAGE_URL
is not used globally: local.appspot.com
cannot be replaced by own server
STORAGE_URL
is not used globally: local.appspot.com
cannot be replaced by own serverSTORAGE_URL
is not used globally: local.appspot.com
is still hardcoded somewhere
See rschroll/rmcl#9 for the changes to |
yep, I've only used rmapi which has the storage urls hardcoded, and only STORAGE_URL has to be correct |
I think deprecating |
rmfakecloud could run either on HTTP and HTTPS, so deprecating Moreover, you can use the For me But 👍 for removing hardcoded |
That is a good objection, I didn't consider @ddvk: If I understand it correctly: Are you ok with including the |
Hi :) can STORAGE_URL contain a subdirectory? or is the most general valid form does the remarkable support http or is it for use with the local forwarding proxy? there are queries that are answerd by the bare hostname, so i guess xochitl/sync adds "https://" |
you are right - that's why the PR is marked as draft :) |
There is no more hardcoded |
Hi,
the function
locateService
in linermfakecloud/internal/app/handlers.go
Line 522 in 3ff893c
STORAGE_URL
, but is instead hardcoded tolocal.appspot.com
.This means that every client of the
rmfakecloud
has to resolve the hostlocal.appspot.com
.Whilst this poses no major problem for the remarkable device itself, it is a nuisance for 3rd-party cloud clients like
rmcl
,rmfuse
, etc: The device running these clients must modify/etc/hosts
and further accept the ca-certificate used to signlocal.appspot.com
.thejonny has drafted a solution already, see #161.
It introduces
STORAGE_HOST
instead ofSTORAGE_URL
(without a precedinghttps://
) and allows us to runrmfakecloud
without manually resolvinglocal.appspot.com
on the remarkable device (or the computer runningrmfuse
).Whilst we are not sure of the precise use of
STORAGE_URL
inrmfakecloud
it might be that is superseeded bySTORAGE_HOST
. But we are not sure yet.The text was updated successfully, but these errors were encountered: