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

Relative content_url path #167

Closed
jbjorge opened this issue Jun 8, 2016 · 3 comments
Closed

Relative content_url path #167

jbjorge opened this issue Jun 8, 2016 · 3 comments
Milestone

Comments

@jbjorge
Copy link

jbjorge commented Jun 8, 2016

Hi Nic, and thanks for creating such a great plugin! It's quite fantastic to be able to push out fixes and changes instantly to my customers!

In my current setup I have one app which all my customers use. Each customer host their own content-server and set the url to that server in the app. From that url I set the config-file-url in JS so the app knows where to fetch its updates. So far, so good.

Here's the challenge
I want to keep a one-to-one relation between my customer's server and the code-instance they run their app on, so that when they update their server, their app gets updated as well.

To accomplish this, I want to host the chcp.json on the same server as chcp.manifest and the app-code for simplicity. Right now, this means that I have to manually set the content_url to match the server's url on each deployment I do.

I don't know if this is an edge-case or if it is already supported, but it would be great if i could set content_url in chcp.json to be relative to chcp.json by doing

content_url: '/relative/path'

So e.g.

"config-file": http://example.com/chcp.json
and
content_url: '/'

means that chcp.manifest (and the files) is located at http://example.com/chcp.manifest

Is this possible or up for consideration for implementing?

@nikDemyankov
Copy link
Member

Hi @jbjorge ,
Thanks :)

The feature that you requested is a good one and I should add it. Something similar is mentioned in issue #161. I think I'll implement it in the version after 1.4, when I'll be focusing on simplifying configuration files.

@jbjorge
Copy link
Author

jbjorge commented Jun 9, 2016

Thanks for the quick reply. It is really reassuring to use a plugin from such an active developer! :)

@nikDemyankov nikDemyankov added this to the v1.5.0 milestone Jun 29, 2016
@nikDemyankov nikDemyankov modified the milestones: v2.0.0, v1.5.0 Aug 29, 2016
@nordnet-deprecation-bot
Copy link
Contributor

👋 Hi! Thank you for your interest in this repo.

😢 We are not using nordnet/cordova-hot-code-push anymore, and we lack the manpower and the experience needed to maintain it. We are aware of the inconveniece that this may cause you. Feel free to use it as is, or create your own fork.

🔒 This will now be closed & locked.

ℹ️ Please see #371 for more information.

@nordnet nordnet locked and limited conversation to collaborators Sep 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants