[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Taler] inline installation limitations / landing page
|
From: |
Christian Grothoff |
|
Subject: |
Re: [Taler] inline installation limitations / landing page |
|
Date: |
Fri, 19 Feb 2016 16:06:02 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 |
On 02/19/2016 01:37 PM, Florian Dold wrote:
> Hi,
>
> I've managed to get inline installation [1] for the Taler WebExtension
> Wallet to work, but there's one problem: It just works on *one* domain
> (not even with subdomains) that is specified in the developer dashboard
> for the application in the chrome webstore.
>
> It would be possible to upload the extension once per (sub)domain where
> we want inline installation, but that's a nightmare ...
>
> Does anybody have thoughts on what is the best way to structure our
> landing page(s) (demo.taler.net and test.taler.net) around that
> limitation? Where do we want the inline installation?
Maybe we should open 'wallet.taler.net'? Just to keep the subdomains
coming? Or, for more sanity, just put 'taler.net'. ;-)
-Christian
signature.asc
Description: OpenPGP digital signature