aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-23 03:57:51 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-23 03:57:51 +0000
commitb701a6dccb9174df0ad9d52166071ea15d0ec33f (patch)
tree41c184d284c66e45484d2029a92e967efb7ce4f0
parent2150b42c825c93cf4dcdeaa4f1c296835cbe65ad (diff)
downloadikiwiki-b701a6dccb9174df0ad9d52166071ea15d0ec33f.tar
ikiwiki-b701a6dccb9174df0ad9d52166071ea15d0ec33f.tar.gz
web commit by JeremyReed: wrapper updated each time
-rw-r--r--doc/bugs/cgi_wrapper_always_regenerated.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/cgi_wrapper_always_regenerated.mdwn b/doc/bugs/cgi_wrapper_always_regenerated.mdwn
new file mode 100644
index 000000000..142a24db2
--- /dev/null
+++ b/doc/bugs/cgi_wrapper_always_regenerated.mdwn
@@ -0,0 +1,7 @@
+I am using --setup with a configuration file that enables my CGI wrapper. This works well. This same configuration also defines the locations of my source and my destination website.
+
+Whenever I run ikiwiki with --setup with this same configuration, then each time my cgi wrapper is updated. It says my cgi is generated and it has new timestamp but md5 shows the file never changed.
+
+Should I use a different config? This is confusing because if I use a config without my cgi wrapper defined, I still have my left-over ikiwiki.cgi still in place (so CGI is enabled).
+
+It seems wasteful to update each time when my goal is just to create the HTML pges (since the CGI didn't generate them) as noted in my other bug report.