dvodvo

Until further notice, i.e. a documented mechanism to run **multiple backend** for an application, the following is a tactical approach to leveraging the Mobility gem.
Motive: consideration of different focus of data - assume global(or central) and local(or decentral) - leads to different polyglot and data requirements locally. One size does not necessarily fit all well.

the key_value backend has its advantages and inconveniences in this context.
*Advantages*
• easily extendible
• good for high volume of translated data
( the other advantages documented here remain true https://dejimata.com/2017/3/3/translating-with-mobility )
*Inconveniences*
• all locale data converges to a single table, which would service the multiple databases of the application

dvodvo

dvodvo

dvodvo

dvodvo

dvodvo

dvodvo

dvodvo

dvodvo

# uploads.rb
CarrierWave.configure do |config|
  config.storage    = :aws
  config.aws_bucket = 'my-bucket-s-name' # name of bucket, no FQDN
  config.aws_acl    = 'private'

  # Optionally define an asset host for configurations that are fronted by a
  # content host, such as CloudFront.
#  config.asset_host = 'http://example.com'

dvodvo

def confirm_ts
   [...]
    else
      set_cart_authorisation(@cart)
      Stripe.api_key = @cart.shop.private_key
      intent = Stripe::PaymentIntent.create({
        amount: @authorisation.to_i,
        currency: 'eur',
        payment_method_types: ['card'],
        capture_method: 'manual',