I'm trying to setup an authentication according to Devise and friends :)
I have added
class Users::SessionsController < Devise::SessionsController
include Tracing
def new
stop_tracer
$ _st | |
12:39:04 - INFO - Guard uses TerminalNotifier to send notifications. | |
12:39:04 - INFO - Guard uses TerminalTitle to send notifications. | |
12:39:04 - INFO - Starting Spork for MiniTest | |
Using MiniTest | |
Preloading Rails environment | |
Loading Spork.prefork block... | |
Rack::File headers parameter replaces cache_control after Rack 1.5. | |
Spork is ready and listening on 8988! | |
12:39:13 - INFO - Spork server for MiniTest successfully started |
I'm trying to setup an authentication according to Devise and friends :)
I have added
class Users::SessionsController < Devise::SessionsController
include Tracing
def new
stop_tracer
A money field supports/depends upon a currency and that introduces the question of what exchange_rate to use!
The simple answer is 1.00000 meaning that the currency gets 'traded' on par - which will satisfy the 'one currency' use case (commonly exchange_rates are listed with 5 decimals - but some currencies requires 7 or more decimals to allowing an accurate calculation, like the Afghani, currently traded against the USD at 0.0206954). One currency use cases could be set using a simple configuration option - like config.money_rails.one_currency_only = true
A somewhat more complex use case is the 'two currencies' application where all money fields are listed (and calculated) in a 'preferred' currency but has to be presented in a secondary currency as well. Some EU-countries have not implemented the Euro as their national currency, like Poland. Their national currency has an almost fixed exchange_rate towards the Euro - it sees fluctuations but only marginally. Money fields are rarely converted but even thoug