wormhole-based signup sometimes lets client proceed too soon

[exarkun]

The current wormhole-based signup gives out a wormhole code as soon as the subscription is recorded in the subscription manager database. The configuration may be transferred over the wormhole at any point after that.

Separately, the subscription converger polls the subscription manager database and deploys infrastructure for new subscriptions.

There's currently no guarantee that the subscription's infrastructure will be deployed before the client picks up their configuration and tries to use it. For example, the domain in the introducer furl location hint may not have been created yet. This causes the client to encounter a failure with a DNS error. The error and failure eventually resolve themselves but in the interim the user may become confused or frustrated.

Ideally, by the time it was possible for the user to try to use their tahoe-lafs configuration, all resources would be in place and the configuration would actually work.

[exarkun]

If the solution involves any kind of waiting on the part of the user with a non-obvious completion point, some kind of progress indicator would be nice.

Chris suggested this thematic progress indicator:

I really like the "We are deploying" bit for the humanistic flair that it adds. :) To capitalize on this further, it would be cool if, in the future, there was an accompanying animation in here somewhere showing a very determined (and possibly very sweaty) POLA bear working away on a server in a data center -- eventually wiping his brow in satisfaction and giving the user a hearty thumb-up when the process completes.. ;)