[Scons-dev] What to replace the wiki with?
Gary Oberbrunner
garyo at oberbrunner.com
Fri Dec 12 12:43:06 EST 2014
On Fri, Dec 12, 2014 at 11:16 AM, Dirk Bächle <tshortik at gmx.de> wrote:
> Gary,
>
> On 12.12.2014 15:00, Gary Oberbrunner wrote:
>
>> I would like to find a system that has some kind of online
>> editor/previewer, rather than a pure clone/edit/push/pull-request system
>> (whether it's git or hg), because sometimes you want to see how your markup
>> will actually look on the site before pushing it. (Dirk, I think that
>> would also help the "occasional contributor" overhead you're concerned
>> about.) I do think something hg or git-based would be preferable.
>>
> sounds acceptable. What I'm mainly after is that a user can queue his
> changes...and then forget about them. So he doesn't have to cycle through
> all kinds of review steps, or answer further inquiries. That might put
> people off...
> It should be "edit", "save/commit"...done.
>
>> And yes, we have to move it off our current hosting provider because DoS
>> attacks on our MoinMoin wiki bring the shared server to its knees on a
>> somewhat regular basis. And I'm not ready to be sysadmin of another amazon
>> micro instance, so we need a hosted solution.
>>
>> Do we have admin access to the host where our website is running on?
> What is it exactly, apached? I just stumbled over this module
>
> http://www.techrepublic.com/blog/smb-technologist/secure-
> your-apache-server-from-ddos-slowloris-and-dns-injection-attacks/
>
No, sadly we don't. Just .htaccess. And I don't think our problems stem
from those kinds of things, though perhaps the first one would help, I
don't know. A lot of it is fake account creation attempts and other probes
based on knowing it's a moinmoin wiki.
> , not sure if it could really help.
>
> Anyway, I have the existing wiki mostly converted from moin to markdown
>> (github flavor, but I could redo it as a different flavor depending on what
>> we choose) with only a few hand edits necessary. Some things like the
>> Bug() macro won't translate, but I think we can live without that. I
>> didn't find any decent tools to convert from moin to rst, so I think going
>> with a markdown solution would be easier than rst at this point, though I
>> think pandoc can convert between markdown and rst, so if needed we can do
>> that -- not sure how lossy that conversion would be.
>>
> There is also Creole ( http://en.wikipedia.org/wiki/Creole_(markup) ),
> which is supported by Bitbucket. I have no personal experience with it, but
> it seems to be designed for exactly this purpose of migrating from one Wiki
> to another
>
I didn't find any translators from moinmoin to creole. I don't think
pandoc can go from markdown (what I have now) to creole yet. BItbucket
also supports markdown though, so if we want to do that it would be easy
(technically). Some folks in this discussion seemed to think it wasn't
great, I don't know. Since I have the markdown pages (or will by the
weekend), I can try pushing up a repo as a bb wiki and we can see how we
like it.
It would be a little odd to have our code at bitbucket and our wiki at
github, but if github's wiki engine/editor is way better, I'd consider it.
After all our wiki has been a separate thing for years already.
--
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20141212/c7605f72/attachment.html>
More information about the Scons-dev
mailing list