Fab
@kennyadsl @tvdeyen given that we are all ok with DB and the amount of work to migrate 1-5 api keys, can we push this into the DB. The work of...
> Yes, it should be doable if those credentials are tied to a store. @tvdeyen bringing this back to an env is a step back from consequent consideration of multistore...
> The proposed usage of preferences sources serves both use cases. It does NOT force any use case to anyone (contrary to the current state of this extension). > Using...
@kennyadsl i think reverting this change is at this point perfectly fine as it seems that env files are the preferred direction and multi store support doesn't seem to be...
@JustShah depending on the preferences of @kennyadsl @tvdeyen either we revert or proceed with the following: - Convert the DB value in a Secure String - offer for all supported...
Have you read this? > @JustShah depending on the preferences of @kennyadsl @tvdeyen either we revert or proceed with the following: > Convert the DB value in a Secure String...
That is correct, as crypto currency codes are not part of the standard. This particular iso standard does not provide anything but official goverment recognized currencies.
@leeran7 @Alireza-Naji had more passion for detail in his response ;)
> Use standard formats: ISO 4217 currency format, e.g. "USD"; Ticker symbol for cryptocurrencies, e.g. "BTC"; well known names for Local Exchange Trading Systems (LETS) and other currency types, e.g....
@tvdeyen is rails 8.0 something that will be done by the maintainers?