Skip to content
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

Maintain a versions.json file tracking the latest per series #6

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

matthewd
Copy link
Member

@matthewd matthewd commented Dec 2, 2015

Also keep a version.js ("static JSONP"), for simple cross-domain access.

@fxn thoughts?

My intention is that we'd arrange for Apache to serve the files directly; I gather this puts them in a place they wouldn't be naturally accessible.

In truth, the "real" JSON file is more of an in-passing side effect... my immediate interest is in the JS file, which could be called from the main website.

Also keep a version.js ("static JSONP"), for simple cross-domain access.
@fxn
Copy link
Member

fxn commented Dec 3, 2015

Which would be the use case? Fetching from http://rubyonrails.org/ to link to different docs?

@rafaelfranca
Copy link
Member

It is being used to show the download link in the rubyonrails.org without having to change that page every time a new release is made.

screen shot 2015-12-03 at 12 48 31 pm

@rafaelfranca
Copy link
Member

:shipit: from me.

@fxn
Copy link
Member

fxn commented Dec 3, 2015

If that's the use case, why not just generating the current stable series. You leave "4.2" somewhere and done.

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

Successfully merging this pull request may close these issues.

3 participants