public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New Wiki Software - Please help testing :)
Date: Sun, 26 May 2019 11:43:20 +0100	[thread overview]
Message-ID: <9A43A250-000E-43B8-A2F0-6B50832525C6@ipfire.org> (raw)
In-Reply-To: <B34E36D5-E87D-4CE5-B364-3FCBCA366F1A@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4258 bytes --]

Hello guys,

Thanks first of all to engage so much in this :)

> On 24 May 2019, at 12:07, Carlo Fusco <fusco.carlo(a)gmail.com> wrote:
> 
> I tried to log in, but I get this error message:
> 
> -------
> Proxy Error
> 
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request POST /login.
> 
> Reason: Error reading from remote server
> ———

This seemed to be caused by a blacklist that we are checking to identify spammers. The blacklist did not seem to respond in time. I have removed that one now and I hope that this will now work better.

Best,
-Michael

> 
>> On 24 May 2019, at 12:58, Carlo Fusco <fusco.carlo(a)gmail.com> wrote:
>> 
>> Hi Michael,
>> 
>> I volunteer to help. One thing I could do is the work necessary to fix the broken links and helping with the manual operations to port the old documents to the new wiki.
>> 
>> Please let me know if there is anything else I can do to assist you.
>> 
>> — 
>> Carlo Fusco
>> 
>>> On 23 May 2019, at 15:35, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>> 
>>> Hello people,
>>> 
>>> I am busy with migrating the wiki to the new webapp.
>>> 
>>> For those who are not aware of this happening: We are going to move away from Dokuwiki. The story is quite a long one, but in short it is that I am unhappy with it. It has been a solid piece of software for us, but the user registration process is broken. People cannot sign up to it. Spam bots can. It does not look very nice and all in all it is written in PHP.
>>> 
>>> The original plan was to port our design to it, but actually it is easier just to write some wiki stuff into the web app where other parts already exist. So I decided to use our web app and add two things: An editor for the pages, a place to upload files and a big function that renders the pages. That is about it.
>>> 
>>> This wiki uses markdown. The syntax is very similar to the Dokuwiki syntax with exception of images, tables and some other smaller things. But markdown is widely used. Loads of people have probably used it somewhere else before. Also this is handy because I did not have to implement something that renders my own syntax.
>>> 
>>> I have been working on a unified account system which is coming along nicely. I have also been working on a converter that is porting all content from Dokuwiki to the new wiki. Unfortunately this is not the easiest thing.
>>> 
>>> The “new” wiki is currently available at https://wiki.dev.ipfire.org/.
>>> 
>>> Please feel free to browse around and have a look what works well and what doesn’t. All in all the converter converts a lot itself and I think the pages look nice and clean. But some things cannot be converted so there might be some stuff that we have to do manually.
>>> 
>>> The biggest of those are tables that do not follow the normal standard. The one on the index page for example is such a table.
>>> 
>>> The second thing that does not work very well is paths. Loads of links are broken and point at arbitrary stuff. The wiki now follows the usual filesystem approach with its URLs (: are / now) and you can go back with “..” and remain in the same directory with “.” or by using no prefix.
>>> 
>>> I also decided not to import the whole history of the wiki. I am not sure if there is any value in it. The data is old and there are tons of images that we no longer need. Also Dokuwiki has a nice API to go through all existing pages and going back into the archive is a bit more difficult.
>>> 
>>> So, please have a look around. Log in. Edit things. I will probably run the import again. Please help me find bugs and send me an email.
>>> 
>>> I would like to switch over as soon as possible.
>>> 
>>> Best,
>>> -Michael
>>> _______________________________________________
>>> Documentation mailing list
>>> Documentation(a)lists.ipfire.org
>>> https://lists.ipfire.org/mailman/listinfo/documentation
>> 
>> — 
>> I will abandon this email address soon, 
>> You can reach me at
>> carlo.fusco(a)pm.me
>> 
>> 
>> 
> 
> — 
> I will abandon this email address soon, 
> You can reach me at
> carlo.fusco(a)pm.me
> 
> 
> 


  reply	other threads:[~2019-05-26 10:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 13:35 Michael Tremer
2019-05-24 10:58 ` Carlo Fusco
2019-05-24 11:07   ` Carlo Fusco
2019-05-26 10:43     ` Michael Tremer [this message]
2019-05-26  8:28 ` Matthias Fischer
2019-05-26 10:54   ` Michael Tremer
2019-05-26 10:55   ` Michael Tremer
2019-06-01 12:09 ` ummeegge
2019-06-02 22:10   ` Michael Tremer
2019-06-06  3:30     ` Jon Murphy
2019-07-16 16:34       ` Michael Tremer
2019-05-24 16:48 Jon Murphy
2019-05-24 22:03 Jon Murphy
2019-05-27 16:27 ` Michael Tremer
2019-05-27 17:10   ` Matthias Fischer
2019-05-30 14:50     ` Michael Tremer
2019-05-28  3:05   ` Jon Murphy
2019-05-30 14:51     ` Michael Tremer
     [not found] <AF378EE0-6263-41AA-A6A0-5442D9C5FCC3@gmail.com>
2019-05-30 14:50 ` Michael Tremer
     [not found] <630732F1-CA01-43FD-8EB5-4601C6BF3162@gmail.com>
2019-05-30 17:07 ` Michael Tremer
2019-05-30 17:22 ` Michael Tremer
     [not found] <0E1A43E9-96F5-487C-8974-ED25DC70D05B@gmail.com>
2019-05-30 17:31 ` Michael Tremer
     [not found] <3917C587-0660-4EA5-A997-081C3A69D045@gmail.com>
2019-05-30 18:17 ` Michael Tremer
     [not found] <4BB6A887-545C-4194-B497-16E08FE82231@gmail.com>
2019-05-30 19:04 ` Michael Tremer
2019-05-30 19:23   ` Jon Murphy
2019-05-30 19:24     ` Michael Tremer
2019-05-30 19:30       ` Jon Murphy
2019-06-02 22:13         ` Michael Tremer
     [not found] <2CAE7946-C451-4D11-B3C6-9C64CAFC1220@gmail.com>
2019-07-17 15:57 ` Michael Tremer
2019-07-17 22:57   ` Jon Murphy
2019-07-18 10:16     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9A43A250-000E-43B8-A2F0-6B50832525C6@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox