1
0
mirror of https://github.com/Mailu/Mailu.git synced 2024-12-12 10:45:38 +02:00
Mailu/setup
lub 1a365f469c check for ipv6_enabled in the compose template
Checking only `ipv6` isn't sufficient, because it has a default value.
2021-02-12 12:18:22 +01:00
..
flavors check for ipv6_enabled in the compose template 2021-02-12 12:18:22 +01:00
static Make setup show external DB parameters automaticaly when selecting postgres 2020-10-12 20:30:26 +02:00
templates mark radio buttons in setup utility as required 2020-10-27 12:52:07 +01:00
.env Revert accidental setup commits and fix code/pre tags 2019-01-28 20:23:41 +01:00
docker-compose.yml Revert accidental setup commits and fix code/pre tags 2019-01-28 20:23:41 +01:00
Dockerfile RPi: fix alpine version for setup, only one layer for pip install 2019-10-09 12:09:18 -04:00
main.py Rename the config dir to setup 2018-04-22 16:10:25 +02:00
README.md Create/generate file template 2018-10-22 12:53:25 +03:00
requirements.txt Prepare setup for multi-ver deployment on docs server 2018-12-16 16:26:45 +02:00
server.py When selecting a non-stable version, add a message this is version is "only for testing". 2020-10-05 09:26:50 +00:00

Adding more flavors/steps

(Everything will go under setup/ directory - using Kubernetes flavor as example)

Until this point, the app is working as it follows:

  • when accesing the setup page it will display the flavors selection step (templates/steps/flavor.html)
  • after you choose your desired flavor it will iterare over the files in the flavor directory and building the page (templates/steps/config.html is general for all flavors)
  • when you complete all required fields and press "Setup Mailu" button it will redirect you to the setup page (flavors/choosen-flavor/setup.html)

To add a new flavor you need to create a directory under templates/steps/ in which you are adding actual steps. Eg: Adding a WIP step we'll create templates/steps/kubernetes/wip.html

Note that wizard.html is iterating over files in this directory and building the page. Files are prefixed with a number for sorting purposes.

wip.html will start with

{% call macros.panel("info", "Step X - Work in progress") %}

and end with

{% endcall %}

You store variable from front-page using the name attribute inside tag. In the example below the string entered in the input field is stored in the variable named var_test

<input type="text" name="var_test">

In order to user the variable furter you use it like {{ var_test }}

In the setup page (flavors/kubernetes/setup.html) you cand add steps by importing macros

{% import "macros.html" as macros %}

and start and end every step with

{% call macros.panel("info", "Step X - Title") %}
-------------------
{% endcall %}

Generating a file

Create the file template in flavors/kubernetes/ (eg. file.txt) in which you save your variables

ROOT = {{ root }}
MY_VAR = {{ var_test }}

When you submit to Setup Mailu the file will be generated. In order to get the file add the following command to setup.html

<p>curl {{ url_for('.file', uid=uid, filepath='file.txt', _external=True) }} > file.txt</p>