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

Ruby version managers #14

Open
ysbaddaden opened this issue Jun 8, 2015 · 0 comments
Open

Ruby version managers #14

ysbaddaden opened this issue Jun 8, 2015 · 0 comments
Labels

Comments

@ysbaddaden
Copy link
Owner

Most of the installation problems Prax users are facing are related to Ruby version managers configuration. Usually, Rack applications won't be started by Prax while running rackup or rails server in the application's directory actually succeeds.

Prax seeks to be version-managers agnostic. Managing which Ruby version to use and where gems are installed is their jobs, and Prax shouldn't have to deal with it; not to mention there are lots of them (RVM, rbenv, chruby, ry, ...). The problem is that this puts the burden on the developers, namely Prax users, which ain't no fun at all for them and may event be a show stopper. Bummer.

The actual question is: should Prax merely provide some documentation on the wiki? should a notice be included in the distributed package, and printed on screen after it's installed? or should Prax actually deal with version managers, checking for their presence in their standard installation places, and automatically configure them? maybe not forcefully, but through a CLI command that would configure ~/.praxconfig?

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

No branches or pull requests

1 participant