summaryrefslogtreecommitdiff
path: root/Gemfile.lock
AgeCommit message (Collapse)Author
2014-01-23added default pricing, privacy policy and tos pages.elijah
2014-01-23updated Gemfile.lockelijah
2013-12-29Return 'provider.json' via a controller, to better be able to control the ↵elijah
response headers (in particular, 'X-Minimum-Client-Version'). It must now be placed in config/provider/provider.json
2013-12-22locale prefix support:elijah
* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path
2013-12-22re-generated Gemfile.lock with the new versions of engine gems. as a side ↵elijah
effect, it also upgraded rails to the the latest in the 3.2 series.
2013-12-20fixed billing tests (added dummy billing hash to config, include required ↵elijah
testing gem phantomjs-binaries)
2013-12-13proceed even if the couch is unreachableAzul
* in case the user has a session id, keep it but proceed without a session * in case we can't initialize the models proceed * if APP_CONFIG[:reraise_errors] is set we'll crash instead in the latter case default to reraise errors in dev and test environments.
2013-12-12use the latest couchrest_session_storeAzul
This one does not use our own error class for connection issues anymore. We'll remove that class in the next commit. So let's not rely on it.
2013-12-09update ruby_core_source so it works with latest ruby versionAzul
2013-12-09update couchrest session store and Gemfile.lockAzul
This will fix the crash when loading the landing page without a couch connection.
2013-11-21rake tasks clean up expired tokens and sessions (#4568)Azul
2013-10-21remove duplicate source line that was using httpAzul
I don't think we need to list the sources again in common_dependencies.rb
2013-10-18include Gemfile.lock to prevent unintended updates (#4174)Azul
We had a broken production server lately because it had upgraded the couchrest model dependency to one that had a different naming scheme for a function we overwrite. So that broke production. Let's prevent that by including the Gemfile.lock in our repositories.
2012-11-12don't track Gemfile.lockAzul
2012-11-04Merge branch 'develop' into feature-warden-srpAzul
Conflicts: Gemfile.lock users/app/controllers/application_controller.rb users/leap_web_users.gemspec
2012-11-04using ruby-srp 0.1.4 - ruby 1.9.3 compatibleAzul
2012-10-30using rails_warden bit of refactoringAzul
without rails_warden the failure app action was not getting set properly.
2012-10-30adding in warden with a basic strategyAzul
currently failing because we are not setting the content-type header.
2012-10-17Merge branch 'develop' into help_developjessib
2012-10-17Not sure we actually want this in version control, but adding changes so ↵jessib
long as we have it.
2012-10-17UI tweaks including newer version of bootstrapAzul
2012-10-11use ruby-srp 0.1.3 which returns the user on authenticate callAzul
Also removed a few hooks to User.current. Will replace with current_user
2012-10-11moved core dependency into */Gemfile with :pathAzul
In order to get the rails generators and the like to work properly in engines we need to require all the dependencies in the engine.rb file. Since I want to keep that list of engines in a centralized place we still need core and we need to require it from the other engines. We don't want to require the core gem to be installed so I added it with :path option to the Gemfile.
2012-10-11first steps at reducing coreAzul
2012-10-08use couchrest session store in core, updated dummy pathAzul
2012-10-08bundle updateAzul
2012-10-08enabling rake gem in engines, using LeapWeb::Version all over the placeAzul
2012-10-05ruby-srp 0.1.1 has to_json method - simplifies controllerAzul
2012-10-05enable therubyracer so we have a js runtimeAzul
2012-10-05removing leap_web_help for version 0.1.0Azul
2012-10-05moving to ruby_srp 0.1.0, works with python srpAzul
2012-10-05adding mocha for testsAzul
2012-10-02commiting changes created by adding helpAzul
2012-09-27using the local path for developmentAzul
this way you do not need to build a gem for changes to take effect.
2012-09-27Adding in what used to be leap webapp demoAzul
we're merging repositories into one