Browser and install GUI for cookiecutter templates

⌈⌋ ⎇ branch:  cookiedough


Artifact [fceeea0c16]

Artifact fceeea0c16971a552a34da6b032d3433006669883e6bcd9b3b0c0038ba03ef73:

Wiki page [rollout] by mario 2021-03-24 09:11:47.
D 2021-03-24T09:11:47.163
L rollout
N text/x-markdown
P 23da4bfbdce72acd3c061ac7a89e5a0e6d890ea5a3f215533e7ee71441298a43
U mario
W 1147
## Roll out

When you hit the **Roll out** button, an input window for the cookiecutter
template will first pop up. Before you the project template gets created,
first edit its properties here.

 * Most input fields are strings. For dropdown boxes it's best to stick
   to the default options.
 * You usually want to leave any `{{expression...}}` as is, because those
   will be expanded by cookiecutter/jinja2.
 * The **Burnin' time!** button will start the project directory creation.

Created project directories will usually reside below the current working
directory. To verify or change your current location, use the **chdir**
button.

### Watch out

See if any prompts come up in the terminal window you started
cookiedough from. Not all click prompts might get captured. And
obviously any error messages would show up there.

> If a OutputDirExistsException or ImportError occurs,
> cookiedough will crash alongside cookiecutter. Makes no sense to capture
> or shorten error messages for what's essentially a programming tool.

When the --verbose setting is enabled, additional output will appear
in any case.

Z 2128616d816135ccf5c6a17e860f71ef