Skip to content
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.

add option to fetchUpdate to use different content_url #249

Closed
pablomaurer opened this issue Nov 16, 2016 · 3 comments
Closed

add option to fetchUpdate to use different content_url #249

pablomaurer opened this issue Nov 16, 2016 · 3 comments

Comments

@pablomaurer
Copy link
Contributor

in chcp.fetchUpdate you can dynamics change the config-file with the options. Would love if I also could pass the content_url there.

Since I have 1 app but different code for each customer, in this way i could generate dynamically all needed urls depending on which customer did log in.

Maybe wait until you begin Issue 161 :D

@nikDemyankov
Copy link
Member

What if you just generate chcp.json on the fly? For example: in the app you define config-file url as https://mydomain.com/chcp?user=_USER_ID_. When put a script on that url, that will read user parameter and generate dynamically chcp.json file with correct content_url. Or even set a custom header instead of url's query parameter.

Maybe wait until you begin Issue 161 :D

Yeah, I really need to jump on that one... Already done some work, but been stuck with bug fixes and some other project.

@pablomaurer
Copy link
Contributor Author

Oh now that's wonderfull great idea :) but I still think this would be a cool option. Now my issue is solved, so feel free to close the issue.

Your doing amazing stuff and this plugin grew up huge, and your still answering every single issue. That's a lot of work :D

@nikDemyankov
Copy link
Member

Thanks :) Although I admit I've been slow lately...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants