-
Notifications
You must be signed in to change notification settings - Fork 494
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
Update to Rails 5 #1087
Comments
Turbolinks 5 will help OSEM a true hybrid application. |
There is no error in upgrading to Rails 5 but is it not better to look up this matter at a later stage as many of the existing gems required for solving other bugs may not be compatible with Rails 5. |
That's precisely the goal of this issue |
I'm going to work on this |
Rails 5 needs at least Ruby 2.2.2, the vagrant installation has 2.1 by default. A way to overcome this is to install rvm or rbenv and use that to install the required ruby version. Is there a simpler method available? |
@AEtherC0r3 sure. distro packages :-) https://build.opensuse.org/project/show/devel:languages:ruby has everything you need |
Hi peeps, We're hoping to do a deployment of a prototype second week of July - do you think this issue is likely to get fixed and closed at least in the git repo (not necessarily a release) within the next 3-4 weeks? Cheers for developing & maintaining this software! |
Hi @stephlocke, we haven't done much progress with Rails 5 lately, as we are currently running 4 projects on GSoC, and we are focusing on those features. @AEtherC0r3 who started working on it is also a GSoC student. That said, the Rails 5 update is definitely something we want to implement - and we will - however I cannot say with certainty when. We are happily accepting contributions if you think you can help speed things up towards that direction. In the meantime feel free to try out our demo http://demo.osem.io/ and keep an eye out on this thread about any progress regarding Rails 5. Thanks, |
Rails 5 is out so we should consider to update Rails in the next future.
The text was updated successfully, but these errors were encountered: