| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
https://rt.cpan.org/Ticket/Display.html?id=74487
Gave up trying to support multiple YAML backends. The XS one requires ugly
manual encoding to get unicode right, and doesn't allow dumping yaml
fragments w/o the yaml header, but at least it doesn't randomly crash
on import like YAML::Mo has started to.
|
| |
|
|
|
| |
This avoids warnings when building a setup file from scratch, in which case
some default settings need to be used.
|
| |
|
|
| |
taint checking happy, but taint checking is disabled.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* Automatically run --gettime the first time ikiwiki is run on
a given srcdir.
* Optimise --gettime for git, so it's appropriatly screamingly
fast. (This could be done for other backends too.)
* However, --gettime for git no longer follows renames.
* Use above to fix up timestamps on docwiki, as well as ensure that
timestamps on basewiki files shipped in the deb are sane.
|
| |
|
|
|
|
|
|
| |
* Rename --getctime to --gettime. (The old name still works for
backwards compatability.)
* --gettime now also looks up last modification time.
* Add rcs_getmtime to plugin API; currently only implemented
for git.
|
| | |
|
| |
|
|
| |
Syck-- it doesn't use unicode by default?! Hello, 2010 calling..
|
| |
|
|
|
| |
YAML is picky about the data ending with a newline, and this makes
it easier to accomplish that
|
| |
|
|
| |
for portabilty to old YAML in Debian stable that lacks the former.
|
| | |
|
| |
|
|
| |
files, such as .htaccess, that would normally be skipped for security or other reasons. Closes: #447267 (Thanks to Aaron Wilson for the original patch.)
|
| |
|
|
| |
destdir, as well as wrappers and the .ikiwiki directory.
|
| |
|
|
|
|
|
|
|
|
| |
Loading and use of IkiWiki::Receive can all be pushed into the git plugin,
rather than scattered around.
I had at first wanted to make a receive plugin and move it there,
but a plugin was not a good fit; you don't want users to have to manually
load it, and making the git plugin load the receive plugin at the right
times would need more, and ugly code.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Was documented to work at command line, but didn't
|
| |
|
|
|
| |
The srcdir is needed by --render, so if --setup is not specified, read it
at the command line.
|
| |
|
|
| |
In this mode, rebuild mode should not be on
|
| |
|
|
|
|
|
| |
The syslog value from the setup file is purposfully ignored when doing
ikiwiki -setup, so that it will output to stdout (while generating wrappers
that do use the syslog). But that caused -dumpsetup to not preserve
the syslog value from the setup file.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This speeds up web commits by 1/4th of a second or so, since perl does
not have to start up for the post commit hook.
perl's locking is completly FuBar, since it's impossible to tell what perl
flock() really does, and thus difficult to write code in other languages
that interoperates with perl's locking. (Let alone interoperating with
existing fcntl locking from perl...)
In this particular case, I think I was able to find a way to avoid the
insanity, mostly. The C code does a true flock(2), and if perl is using an
incompatable lock method that does not use the same locking primative at
the kernel level, then the C code's test will fail, and it will go ahead
and run the perl code. Then the perl code's test will test the right thing.
On Debian, at least lately, perl's flock() does a true flock(2), so the
optimisation does work.
|
| |
|
|
|
| |
This saves around 1/4th second per trusted commit since ikiwiki
doesn't need to start up.
|
| |
|
|
| |
Still need to investigate possible races, and test some more.
|
| |
|
|
|
| |
Wired up check_canedit and check_canremove, still need to deal with
check_canattach, and test.
|
| |\ |
|
| | |
| |
| |
| | |
plugins. (Particularly a win when using external plugins.)
|
| |/
|
|
|
| |
Still need to wire up the calls to check_* , but it's cold out here and my
hands are going numb, so enough for now.
|
| | |
|
| |
|
|
|
| |
If run w/o --refresh, it should still say "refreshing wiki", if there's no
setup file specifed.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
enables syslog.
Setup output is once again output to stdout in this case.
Implemented by stashing the verbose/syslog values set in the setup file,
and using those values in the generated wrappers, but not allowing them to take
effect during the setup operation itself, so that command-line options,
appearing before or after -setup, are honored.
Also, some cleanups to how %config is generated for wrappers, removing some
fields that do not need to be recorded inside the wrapper.
|
| |
|
|
| |
specified.
|
| |
|
|
| |
This allows later switches to override them. Previously, setup file options overrode most command line options.
|
| |
|
|
| |
This makes reentrant ikiwiki calls from wrappers work.
|
| |
|
|
|
| |
Setting to undef rather than 0 means that setup files generated from
the cgi wrapper will not have verbose set to 0, but instead commented out.
|
| |
|
|
| |
This reverts commit c8d3626c51bdc53781d9431b1da88ae1e92dc2d5.
|
| | |
|
| |
|
|
| |
Necessary now that the plugins control what wrappers are built.
|
| |
|
|
|
| |
shortcut tried to use srcdir in checkconfig; change it to not so this will
work.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|