1 I just went through the standard procedure described for setup, copied the blog directory from examples into my source directory, ran ikiwiki, and everything seems to have worked, except that none of the
2 [[!meta ... ]] tags get converted. They simply show up in the html files unformatted, with no exclamation point, and with p tags around them. Any ideas? using ikiwiki version 2.40 on freebsd --mjg
4 > The meta plugin is not enabled by default. It's pulled in by the
5 > goodstuff plugin, so add one or the other to the add_plugins line in your
6 > config file. --[[Joey]]
8 Can the instructions for using `ikiwiki-makerepo` be clarified. This
9 command wants to create folders in the directory it is run in. Which
10 directory should that be - `$SRCDIR?` --Andy
12 > No, `ikiwiki-makerepo` does not create directories in the current
13 > directory. You specify the directory you want it to create and it creates
14 > the directory and makes it into a repository. The setup instuctions have
15 > examples of doing this. I don't see anything unclear. --[[Joey]]
17 Sorry, was not precise enough. It does if you are using the git option. I
18 believe this is partially explained on the rcs/git/ page. However I'm still
19 not totally clear where I should run the command when using git. If I
20 should be in $SRCDIR then updating the instructions to something like
24 ikiwiki-makerepo git $SCDIR $REPOSITORY
26 might clear things up a little. Apologies if I'm being a bit dim, learning
27 ikiwiki and git at same time :)
31 1. mkdir $REP cd $REP run command (says $REP already exists so won't run)
32 2. rm -rf $REP cd $SRC run command (creates a repository in $SRC, does not create $REP ends with "remote origin already exists"
33 3. mkdir $TMP cd $TMP run command (creates a repository in $SRC/.git creates a repository in $TMP, does nothing to $REP, ends with "remote origin already exists".
35 Version of ikiwiki installed is package from Ubuntu/Hardy 2.19
36 Git version is 1.5.2.5
38 n.b. svn version of command worked fine :)
42 > Initialized empty shared Git repository in /home/deploy/tmp/
43 > Initialized empty Git repository in .git/
44 > fatal: '/home/deploy/tmp/repo': unable to chdir or not a git archive
46 Looks like your git does not support GIT_DIR being used with git-init. I
47 see some mentions of changes in git's changelog for 1.5.3 that look
48 relevant. I've changed ikiwiki-makerepo to use a method more portable to
49 older versions of git. --[[Joey]]
51 Many thanks Joey, upgraded my git, and now have working iki :) -- Andy
55 It isn't intended that .ikiwiki be versioned, is it? Do you have a svn:ignore set?
56 Is there some magic way you can make the svn commands (and presumably commands for
57 the other VCSs here) ignore the .ikiwiki directory during step 8, when they import it?
58 If not, maybe a note should be made that the user should delete this file before
61 > No, .ikiwiki should not be versioned, and a svn:ignore of it is reasonable,
62 > although probably too much noise for the setup instructions.
63 > I've switched to a different method that preserves .ikiwiki, w/o checking
68 These instructions should probably show how to use a bare Git repository
69 (`GIT_DIR=somewhere.git git-init-db`) rather than a repository with a full
70 working copy. You can always clone the repository if you want your own local
71 working copy. Furthermore, this allows you to make multiple commits to your
72 working copy before pushing them to the repository and causing the wiki to
73 update. --[[JoshTriplett]]
75 > I'm currently testing and running such a setup. --[[tschwinge]]
77 Furthermore the git instructions should be changed to move the *.ikiwiki*
78 directory back into the wiki's working copy directory, isn't it? --[[tschwinge]]
80 > Yes, I think so. I will clean these instructions up unless somebody tells me we're missing something fundamental. --[[BartMassey]]
82 >> Either you do it or I'll do it somewhen soon. --[[tschwinge]]
86 Curious as to why support for CVS is not built in. --[[Luther]]
88 > See [[todo/CVS_backend|todo/CVS_backend]], but you might consider switching to a better version control system. --[[JoshTriplett]]
92 What is the syntax for specifying the adminuser as an openid user? I've tried a couple things but I'm missing something. Thanks for any pointers. -- [[AdamShand]]
94 > Just put the openid url in there. It has to be the full url with
95 > "http://". --[[Joey]]
99 I apologize if this is the incorrect forum for this question, but I am trying to get ikiwiki set up and running with git. I followed all the directions and all seems to work until I go back and try to make changes. The steps I am performing:
101 cd $SRCDIR (e.g. ~/ikisrc)
102 vim index.mdwn (add a couple lines)
103 git commit -a -m 'test'
106 I then get a long error message which reads in part "You asked me to pull without telling me which branch you
107 want to merge with, and 'branch.master.merge' in your configuration file does not tell me either." From that point on, I get:
109 sws@odin:~/dev/ikisrc$ git push
110 To /home/git/repos/myikiwiki.git
111 ! [rejected] master -> master (non-fast forward)
112 error: failed to push to '/home/git/repos/myikiwiki.git'
114 If I do a git clone ssh://odin/path/to/$REPOSITORY from another machine and try to edit I get the same error sequence. What am I doing wrong?
118 I follow every steps of the setup procedure, change some templates and tried to modify some page through the web but was not able to do so. Every page seems to be locked by the adminuser user. When I remove the adminuser in the setup file, every ran fine. Did I miss something ? What is exactly the adminuser supposed to be allowed to ? Is he the only user allowed to modify pages ?
120 > This was a bug in ikwiki that was fixed in version 2.44. --[[Joey]]
123 I hope you guys can put up with an absolute newbie. I am fairly new to linux and completely new to Perl. I have just installed MoinMoin locally in my PC, running ubuntu 8.4 and was about to use it until I ran into your ikiwiki. I thought ikiwiki is a better fit for what I want to do, so am seriously considering installing it as well in ubuntu. Except that the install seems way beyond my understanding.
125 Do i need to install git first? Which git -- the git-core? Ubuntu's instructions on installing the git-core is: "sudo apt-get install git-core". Is that it? Do I need to do a git-init as well, or will the ikiwiki-makerepo handle that? If I have to do a git-init as well, what --share values should I specify?
127 It seems I will have to install the ikiwiki from the tar.gz file. I have downloaded it, but do I need to install CPAN or CPAN++ first? That doesn't sound right. I am totally confused already. Does anyone have some install documents pitched to someone as ignorant as I am? -- [[WillDioneda]]
129 > Ubuntu includes ikiwiki (in universe, I assume), so you should just be
130 > able to use apt or synaptic to install the package, as documented on the
131 > [[download]] page. Install git-core also to get git.
133 > You do not need to use git-init if you use ikiwiki-makrepo. --[[Joey]]
136 Thanks for your response. You're right. Ubuntu does have ikiwiki, except that it is an older version. I tried installing it; saw some error messages from the install, and decided against it. Plus the documentation here in ikiwiki.info seems slightly different. I made an executive/beginner decision: to go for the latest tarball. And found myself in deep water, ...
138 Anyway, I think I might be able to install it from the tarball I downloaded. I've been reading the discussions, had a look at your screencasts, etc. I will give it another bash. -- [[WillDioneda]]
142 How do I set up cgi editing? In setup I have:
144 * cgiurl => 'http://wiki.had.co.nz/edit.cgi'
145 * cgi_wrapper => 'edit.cgi'
147 But I don't get an edit link on my pages? What am I doing wrong?
149 > Assuming you don't have the editpage plugin disabled, all you should need
150 > to so is re-run `ikiwiki -setup` with the above config and it should
151 > rebuild your wiki and add the edit links to pages. --[[Joey]]