https hosting of the JSON schema specs?

[michielbdejong]

i think it looks kinda cool to have the JSON schemas on https, but then we do need to get https hosting for it.

so options:

1. get https hosting for https://remotestoragejs.com/ somewhere. @nilclass do you have a free IP address on the heahdk server maybe?
2. same, but moving the specs (and docs) to the (way cooler!) https://remotestorage.io/ domain
3. change the schema base-location to just be on http://remotestorage[js.com|.io] instead of using the current https URIs.

but right now the self-documenting pages we advertise in our schemas don't actually exist. :)

[raucao]

I vote for hosting them somewhere with CORS and using JS on remotestorage.io to have a nice browsable directory with good formatting, interactive examples, etc.

[jancborchardt]

Yes, I guess with whichever new stuff it’s probably best to use the .io domain and slowly phase out the js.com one.

On Sat, Feb 9, 2013 at 12:50 PM, Sebastian Kippe notifications@github.comwrote:

I vote for hosting them somewhere with CORS and using JS on remotestorage.io to have a nice browsable directory with good formatting, interactive examples, etc.

— Reply to this email directly or view it on GitHubhttps://github.com/RemoteStorage/remotestorage.io/issues/40#issuecomment-13330255..

[michielbdejong]

ok, and let's just use http for the URIs then, since https hosting is so difficult. so then the URIs will change from e.g.:

https://remotestoragejs.com/spec/modules/email/credentials

(which is currently a non-existing file) to e.g.:

http://remotestorage.io/spec/modules/email/credentials

which we could easily deploy. i'm fine with that, whatever is most practical. @nilclass can you dictatorize a quick and final decision on this?

[raucao]

No, we cannot use the main domain, because we cannot route stuff there, and we don't want to commit code to the website repo. We should have sth like schema.remotestorage.io, which could then also easily use https, when we host it somewhere other than GH pages.

[silverbucket]

+1

On Tue, Feb 12, 2013 at 5:19 PM, Sebastian Kippe notifications@github.comwrote:

No, we cannot use the main domain, because we cannot route stuff, and we don't want to commit code to the website repo. We should have sth like schema.remotestorage.io, which could then also easily use https, when we host it somewhere other than GH pages.

— Reply to this email directly or view it on GitHubhttps://github.com/RemoteStorage/remotestorage.io/issues/40#issuecomment-13440433.

[raucao]

Let's discuss this on IRC or the forums and open a new issue or pull request then.