[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Taler] Taler dev setup

From: Lukas Großberger
Subject: [Taler] Taler dev setup
Date: Fri, 3 May 2019 08:42:55 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

Dear Taler community,

I had great fun working on the web-common, auditor and landing repo.
With these it's fairly straight forward to run / build them stand alone,
locally. Especially with the extended README instructions that you
provided along the way, thanks again.

With other more elaborate setup procedures, e.g. for the donations or
blog repo, it seems like the setup is dependent on a fairly specific
environment (e.g. doesn't work if the Python environment happens to be
an Anaconda environment). These are fair assumptions made, I'd say.
Especially for a service that is not meant to be run on a very
heterogeneous group of machines. I'm now just wondering about your best
practices for setting up a Taler development environment.
1) Is it feasible and reasonable to set up every repo stand alone? This
would make it easier for people starting out to contribute to Taler. If
so, can we jointly create documentation for each repo on how to do this?
2.1) How do you, core developers, set up your local development
environment? Do you have one dedicated machine where you do the system
wide setup and nothing else, a VM, possibly a dockerized version?
2.2) How do you deal with submodule dependencies when you are actually
developing on the submodule? I now symlinked to web-common in place of
the original submodule, which seems hacky.

I'm looking forward to diving in deeper into all the Taler components :)

Thanks, Lukas

reply via email to

[Prev in Thread] Current Thread [Next in Thread]