You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
orrails 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
?The text was updated successfully, but these errors were encountered: