Even if this was the original goal, we have evolved the discussion. If we
are looking for ease of use, features, and ease of admin, why stick to a
specific language? I don't happen to like perl - or know much about it, for
that matter - so I can just as easily go with a non-perl wiki...


On Mon, Apr 8, 2013 at 9:20 AM, Yaron Shahrabani <[email protected]> wrote:

> I thought that the whole point of using IkiWiki was to avoid using PHP,
> correct me if I'm wrong.
>
> Yaron Shahrabani
>
> <Hebrew translator>
>
>
>
> On Mon, Apr 8, 2013 at 7:20 AM, Steve G. <[email protected]> wrote:
>
>> You can use PmWiki, which is in php, can be used with or without mysql or
>> another database, is very easy to maintain, can be edited online.
>>
>> It has multi-level granularity, you can give people access to edit
>> individual pages or groups of pages, etc. As far as I remember it has 3-4
>> permission levels, from read permission, to edit, to approve pages (for
>> editors/admins) to set passwords and administer the system.
>>
>> I have been using it for years without any problems and I am far from an
>> advanced user, coder or sysadmin. I am sure there are other light footprint
>> and established wikis.
>>
>> Z.
>>
>>
>> On Sun, Apr 7, 2013 at 6:49 PM, Amir Eldor <[email protected]> wrote:
>>
>>> Hello Shlomi and CC'ed list,
>>>
>>> We have started playing around with IkiWiki on one of our servers. As I
>>> see it, there's a drawback of tough installation and possibly annoying
>>> maintenance. Not sure if I will have enough time to deal with bugs or
>>> problems in a timely manner if we are not to use HaMakor's funds for paid
>>> IkiWiki services. The good things about IkiWiki is the ability to edit the
>>> wiki online and its plugin system (although I'm not sure what plugins we
>>> need).
>>>
>>> The alternative is to not shoot myself in the leg by using a Perl system
>>> for the job (although Shlomi likes Perl) and use a different solution
>>> instead. Two possibles are either making a small compiler-script that
>>> converts Markdown/whatever to HTML and version it with git/whatever. This
>>> is pretty close to using the second alternative which is something like the
>>> Ruby based like "serve <http://get-serve.com/>". The +'s, easier to
>>> administer than IkiWiki. The -'s, no online editing. The ?'s - do we want
>>> Wiki-like editing on Linux.org.il? or can we settle down with having
>>> the sources on GitHub/BItBucket and accepting pull-requests instead of wiki
>>> edits?
>>>
>>> Would like to hear your input,
>>>   Amir
>>>
>>> _______________________________________________
>>> Discussions mailing list
>>> [email protected]
>>> http://hamakor.org.il/cgi-bin/mailman/listinfo/discussions
>>>
>>
>>
>>
>> --
>> Sincerely,
>>
>> Steve
>>
>> http://www.words2u.net - GPS points and tracks (mainly in Costa Rica)
>>
>> http://www.words2u.net/recipes - Recipe collection
>>
>> _______________________________________________
>> Discussions mailing list
>> [email protected]
>> http://hamakor.org.il/cgi-bin/mailman/listinfo/discussions
>>
>
>


-- 
Sincerely,

Steve

http://www.words2u.net - GPS points and tracks (mainly in Costa Rica)

http://www.words2u.net/recipes - Recipe collection
_______________________________________________
Discussions mailing list
[email protected]
http://hamakor.org.il/cgi-bin/mailman/listinfo/discussions

לענות