Added a comment: Solution

diff --git a/doc/forum/Non-interactive_setup/comment_1_e3b9539939a8b0dd3f912a3410dd27b2._comment b/doc/forum/Non-interactive_setup/comment_1_e3b9539939a8b0dd3f912a3410dd27b2._comment
new file mode 100644 (file)
index 0000000..6e8b67c
--- /dev/null
+++ b/doc/forum/Non-interactive_setup/comment_1_e3b9539939a8b0dd3f912a3410dd27b2._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="ac_w"
+ avatar="http://cdn.libravatar.org/avatar/a76f89f70fffde5fbdacaa2a0438d8d9"
+ subject="Solution"
+ date="2021-05-11T14:00:34Z"
+ content="""
+I didn't fully understand it at first, but when you do `ikiwiki --setup /etc/ikiwiki/auto.setup`, the user `foo.setup` that is generated is enough to rebuild the wiki from scratch. So from a fresh reinstall the auto.setup step can be avoided if you already have the previous `foo.setup` backed up.
+
+So on my ansible usecase I just have to keep `foo.setup` as a template, copy it and build the wiki.
+
+I don't know if this creates a wiki administrator though. I guess it doesn't, since the foo.setup contains no info about it.
+
+If I really wanted to create an admin and choose its password, I guess I would have to run the `ikiwiki --setup /etc/ikiwiki/auto.setup`, and in this case the `expect` module from ansible would allow me to send the password to fill the prompt automatically (not tested). Seems kinda hacky though.
+"""]]