I will mark this as WIP as long as #2174 is not merged because #2174 is important. You will then likely need to rebase onto master. Reviews can then be provided. In the meantime, I'd like to discuss this topic in the linked issue #2178.

I have adjusted to documentation :) @polarathene what do you think of this PR?

@wernerfred I messed up setup.sh for a second with one of my commits. Please review again :)

NOTE Tests for merge requests are currently expected to fail. When #2189 is merged, tests should pass again.

setup.sh is non-interactive and all configuration is based on parameters. Why switching to interactive for podman?

This makes it harder, if you use setup.sh in an automated way. There should be an "rootless" option, when calling setup.sh.

setup.sh is non-interactive and all configuration is based on parameters. Why switching to interactive for podman?

This makes it harder, if you use setup.sh in an automated way. There should be an "rootless" option, when calling setup.sh.

Agreed. I thought about exactly the same when doing the change. But should be done with another PR :)

Unexpected test failure:

 not ok 296 checking system: postfix should not log to syslog
# (from function `assert_failure' in file test/test_helper/bats-assert/src/assert.bash, line 140,
#  in test file test/tests.bats, line 549)
#   `assert_failure' failed
# 
# -- command succeeded, but it was expected to fail --
# output : Sep 16 09:33:13 mail postfix/postfix-script[2669]: fatal: the Postfix mail system is already running
# --
# 

Re-run the tests?

But should be done with another PR :)

Why not change it now?

@wernerfred I'd rather like to have a look at the whole "argument" parsing TBH. Therefore, I'd like to see the functionality being preserved with this PR and change with a follow-up.

I have completely removed the changes to setup.sh as I will provide a dedicated PR for that.

Documentation preview for this PR is ready! 🎉

Built with commit: 484b30d