4 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

As a long-time MediaWiki user, I would like to start a new wiki project because I really appreciate MediaWiki maturity and very flexible and powerful capabilities. But I have doubts that I want to take all of MediaWiki infrastructure on board for the new project.

Let's say, I would really like to have a VCS backend to have all wiki edits in one place. As far as I know, MediaWiki supports RBDMS backends only. I've recently came across an old questionold question asked about four years ago. After playing a while with Gitit and Ikiwiki, I feel that Gitit is a better choice allowing integration with GIt or Mercurial, and it's not a static compiler unlike Ikiwiki. Gitit seems to be a much lighter solution than MediaWiki, however I'm afraid it's not even a 10% powerful comparing to MediaWiki: I couldn't compare revisions through the web interface, not sure if I can use categories or templates that are crucial to me, just a few plugins. But I really love the idea of having a VCS backend, because I can sync with the backend locally, can easily export it and use all Git or Mercurial features.

I do remember there is a Git remote helper for MediaWiki that is a bridge-like solution between MediaWiki API over HTTP and Git. I tested it as well, and I had a strong feeling that this Git extension is very raw and seemed to work very slow causing even restart Git cloning in some cases (probably due to the real wiki performance, not sure), and probably might cause another issues. I had never managed to get a full history dump unfortunately.

Is there a way of using Git or Mercurial as a real MediaWiki backend?

EDIT:

I seem to look for an easy Wiki full data replication solution (must have: articles, talk pages, templates, files; optional: probably user database (assuming the VCS stores the user info itself, or maybe something like Mercurial ACL, whatever) and other minor things that aren't tightly related to the wiki content per se) along with an easy to migrate infrastructure.

As a long-time MediaWiki user, I would like to start a new wiki project because I really appreciate MediaWiki maturity and very flexible and powerful capabilities. But I have doubts that I want to take all of MediaWiki infrastructure on board for the new project.

Let's say, I would really like to have a VCS backend to have all wiki edits in one place. As far as I know, MediaWiki supports RBDMS backends only. I've recently came across an old question asked about four years ago. After playing a while with Gitit and Ikiwiki, I feel that Gitit is a better choice allowing integration with GIt or Mercurial, and it's not a static compiler unlike Ikiwiki. Gitit seems to be a much lighter solution than MediaWiki, however I'm afraid it's not even a 10% powerful comparing to MediaWiki: I couldn't compare revisions through the web interface, not sure if I can use categories or templates that are crucial to me, just a few plugins. But I really love the idea of having a VCS backend, because I can sync with the backend locally, can easily export it and use all Git or Mercurial features.

I do remember there is a Git remote helper for MediaWiki that is a bridge-like solution between MediaWiki API over HTTP and Git. I tested it as well, and I had a strong feeling that this Git extension is very raw and seemed to work very slow causing even restart Git cloning in some cases (probably due to the real wiki performance, not sure), and probably might cause another issues. I had never managed to get a full history dump unfortunately.

Is there a way of using Git or Mercurial as a real MediaWiki backend?

EDIT:

I seem to look for an easy Wiki full data replication solution (must have: articles, talk pages, templates, files; optional: probably user database (assuming the VCS stores the user info itself, or maybe something like Mercurial ACL, whatever) and other minor things that aren't tightly related to the wiki content per se) along with an easy to migrate infrastructure.

As a long-time MediaWiki user, I would like to start a new wiki project because I really appreciate MediaWiki maturity and very flexible and powerful capabilities. But I have doubts that I want to take all of MediaWiki infrastructure on board for the new project.

Let's say, I would really like to have a VCS backend to have all wiki edits in one place. As far as I know, MediaWiki supports RBDMS backends only. I've recently came across an old question asked about four years ago. After playing a while with Gitit and Ikiwiki, I feel that Gitit is a better choice allowing integration with GIt or Mercurial, and it's not a static compiler unlike Ikiwiki. Gitit seems to be a much lighter solution than MediaWiki, however I'm afraid it's not even a 10% powerful comparing to MediaWiki: I couldn't compare revisions through the web interface, not sure if I can use categories or templates that are crucial to me, just a few plugins. But I really love the idea of having a VCS backend, because I can sync with the backend locally, can easily export it and use all Git or Mercurial features.

I do remember there is a Git remote helper for MediaWiki that is a bridge-like solution between MediaWiki API over HTTP and Git. I tested it as well, and I had a strong feeling that this Git extension is very raw and seemed to work very slow causing even restart Git cloning in some cases (probably due to the real wiki performance, not sure), and probably might cause another issues. I had never managed to get a full history dump unfortunately.

Is there a way of using Git or Mercurial as a real MediaWiki backend?

EDIT:

I seem to look for an easy Wiki full data replication solution (must have: articles, talk pages, templates, files; optional: probably user database (assuming the VCS stores the user info itself, or maybe something like Mercurial ACL, whatever) and other minor things that aren't tightly related to the wiki content per se) along with an easy to migrate infrastructure.

    Post Closed as "off-topic" by Stephen Ostermiller
3 edited title
| link

MediaWiki VCS backend? (Preferrably DCVSDVCS like Git or Mercurial)

2 minor
source | link

MediaWiki VCS backend? (Git,Preferrably DCVS like Git or Mercurial) backend?

As a long-time MediaWiki user, I would like to start a new wiki project because I really appreciate MediaWiki maturity and very flexible and powerful capabilities. But I have doubts that I want to take all of MediaWiki infrastructure on board for the new project.

Let's say, I would really like to have a VCS backend to have all wiki edits in one place. As far as I know, MediaWiki supports RBDMS backends only. I've recently came across this old question:an http://stackoverflow.com/questions/8255749/wikis-with-vcs-backendsold question (4 yrsasked about four years ago). After playing a while with Gitit and Ikiwiki, I feel that Gitit is a better choice allowing integration with GIt or Mercurial, and it's not a static compiler unlike Ikiwiki. Gitit seems to be a much lighter solution than MediaWiki, however I'm afraid it's not even a 10% powerful comparing to MediaWiki: I couldn't compare revisions through the web interface, not sure if I can use categories or templates that are crucial to me, just a few plugins. But I really love the idea of having a VCS backend, because I can sync with the backend locally, can easily export it and use all Git or Mercurial features.

I do remember there is a Git remote helperGit remote helper for MediaWiki that is a bridge-like solution between MediaWiki API over HTTP and Git. I tested it as well, and I had a strong feeling that this Git extension is very raw and seemed to work very slow causing even restart Git cloning in some cases (probably due to the real wiki performance, not sure), and probably might cause another issues. I had never managed to get a full history dump unfortunately.

Is there a way of using a Git or Mercurial as a real MediaWiki backend?

EDIT:

I seem to look for an easy Wiki full data replication solution (must have: articles, talk pages, templates, files; optional: probably user database (assuming the VCS stores the user info itself, or maybe something like Mercurial ACL, whatever) and other minor things that aren't tightly related to the wiki content per se) along with an easy to migrate infrastructure.

MediaWiki VCS (Git, Mercurial) backend?

As a long-time MediaWiki user, I would like to start a new wiki project because I really appreciate MediaWiki maturity and very flexible and powerful capabilities. But I have doubts that I want to take all of MediaWiki infrastructure on board for the new project.

Let's say, I would really like to have a VCS backend to have all wiki edits in one place. As far as I know, MediaWiki supports RBDMS backends only. I've recently came across this old question: http://stackoverflow.com/questions/8255749/wikis-with-vcs-backends (4 yrs ago). After playing a while with Gitit and Ikiwiki, I feel that Gitit is a better choice allowing integration with GIt or Mercurial, and it's not a static compiler unlike Ikiwiki. Gitit seems to be a much lighter solution than MediaWiki, however I'm afraid it's not even a 10% powerful comparing to MediaWiki: I couldn't compare revisions through the web interface, not sure if I can use categories or templates that are crucial to me, just a few plugins. But I really love the idea of having a VCS backend, because I can sync with the backend locally, can easily export it and use all Git or Mercurial features.

I do remember there is a Git remote helper that is a bridge-like solution between MediaWiki API over HTTP and Git. I tested it as well, and I had a strong feeling that this Git extension is very raw and seemed to work very slow causing even restart Git cloning in some cases (probably due to the real wiki performance, not sure), and probably might cause another issues. I had never managed to get a full history dump unfortunately.

Is there a way of using a Git or Mercurial as a real MediaWiki backend?

MediaWiki VCS backend? (Preferrably DCVS like Git or Mercurial)

As a long-time MediaWiki user, I would like to start a new wiki project because I really appreciate MediaWiki maturity and very flexible and powerful capabilities. But I have doubts that I want to take all of MediaWiki infrastructure on board for the new project.

Let's say, I would really like to have a VCS backend to have all wiki edits in one place. As far as I know, MediaWiki supports RBDMS backends only. I've recently came across an old question asked about four years ago. After playing a while with Gitit and Ikiwiki, I feel that Gitit is a better choice allowing integration with GIt or Mercurial, and it's not a static compiler unlike Ikiwiki. Gitit seems to be a much lighter solution than MediaWiki, however I'm afraid it's not even a 10% powerful comparing to MediaWiki: I couldn't compare revisions through the web interface, not sure if I can use categories or templates that are crucial to me, just a few plugins. But I really love the idea of having a VCS backend, because I can sync with the backend locally, can easily export it and use all Git or Mercurial features.

I do remember there is a Git remote helper for MediaWiki that is a bridge-like solution between MediaWiki API over HTTP and Git. I tested it as well, and I had a strong feeling that this Git extension is very raw and seemed to work very slow causing even restart Git cloning in some cases (probably due to the real wiki performance, not sure), and probably might cause another issues. I had never managed to get a full history dump unfortunately.

Is there a way of using Git or Mercurial as a real MediaWiki backend?

EDIT:

I seem to look for an easy Wiki full data replication solution (must have: articles, talk pages, templates, files; optional: probably user database (assuming the VCS stores the user info itself, or maybe something like Mercurial ACL, whatever) and other minor things that aren't tightly related to the wiki content per se) along with an easy to migrate infrastructure.

    Tweeted twitter.com/#!/StackWebmasters/status/611782642346913792
1
source | link