flowrakis-taler_nuxt-module
v0.131.3
Published
Add privacy aware GNU Taler Payments to your nuxt projects
Maintainers
Readme
flowrakis GNU Taler Payment and Donation Module for nuxt
A GNU Taler Payment Module for Nuxt/Vue.js.
Module to easily add direct GNU Taler support into your Nuxt project.
This project is kindly supported by NGI Taler by the NGI Initiative. And if you have great FOSS ideas, maybe you really should have a look at their open calls right now.
Enlisting to the Nuxt Module List is currently on its way under https://github.com/nuxt/modules/issues/1461
What is GNU Taler?
The GNU Taler is a privacy-preserving digital payment system which could be dubbed as the digital online equivalent to analogue offline cash. It allows for anonymous payments and is very fast and easy on the resources. It it something quite different than Crypto, because it is not itself a Currency, but a mathematically secured protocol to transfer amounts of potentially any currency.
Currently you can actually convert Swiss Franks CHF into Taler as https://taler-ops.ch/en/index.html - Germany is due next to support EUR exchange.
Alternatively you could set up your own local currency with your self-hosted taler bank just like the local alternative currency NetzBon does it.
Demo
You will find a demo at https://nuxt-module.taler.flowrakis.eu/ where you can actually pay with $KUDOS. However, the /admin route is protected, and for that to test you need to install it locally.
Quick Starts
Run the Playground
Just clone the package repository from https://www.npmjs.com/package/flowrakis-taler_nuxt-module and start it
$ git clone https://open.code.flowrakis<eu/flowrakis/flowrakis-taler_nuxt-module.git>
$ cd flowrakis-taler_nuxt-module
$ npm run dev
Install & Integrate the Module into your Project
Install the package from npm
$ npm install --save flowrakis-taler_nuxt-module # or better use pnpm.
Add the module to your `/nuxt.config<js/`>
export default defineNuxtConfig({
, modules:[ 'flowrakis-taler_nuxt-module' ]})Add a Donation Component to your Nuxt Project
<template>
<flowrakisDonationForm />
</template>Now your project can already accept donations. Howeve, without some configuration it will all go to the sandbox.
Configuration
Online
<template>
<flowrakisAdmin_talerMerchantBackendConnection
flowrakisApi="/api/flowrakis/admin/payment-provider" /></template>Currently the modules provides no authentication, so you need to take care of adequate protection.
Build Time
You can configure your credentials in a local json file within or above your projectfolder and/or add your own admin panel as demonstrated in the play ground. Enter the acquired credential them in a file above your project older called ../flowrakisSecrets.json. This would look something like this:
{"talerMerchantBackendConnectionArray": [ {
"talerMerchantId": "merchant-1ab2c3d4"
, "talerMerchantToken": "1a2b3c4d5e6f"
, "talerMerchantFullName": "your-name"
, "flowrakisCurrency": "$KUDOS"
, "talerMerchantInstanceHostUrl": "https://backend.demo.taler.net"}]}Deeper Reading
You find ore details such as api documentation in in the README.DEEPER.md file.
About flowrakis
flowrakis is a human-first coding and collaboration philosophy. As a anglo-greek neologism it literally means The Little Flow and comes with a few adamant principles. All flowrakisCode is hand-written, for instance. Of course we cannot guarantee that there is only human code in all the libraries we use. And we also use LLM's to code, but only under different termspaces. So while we love the oppertunities , that LLM's bring to coding, we think it's a very good idea to keep things a little separeted.
In coding practice flowrakis serves as a semantically safe termpsace, where every so called flowrakisTerm has one unambiguous, clear and distinct meaning. For instance, a flowrakisSet will always denote a set of elements in the mathematical sense, never the setting of a property value. For that we would use flowrakisLet , and so on.
As a coding and naming convention it works quite simply by prefixing almost every identifier, member or variable but particularily and consistently on every export or function signature.
