Talk:Software bundles

.

Is there a web-based application for MediaWiki? That is, I am a non-technical user and don't want to have to worry about the technical issues of hosting my wiki even with the help of an appliance. —The preceding unsigned comment was added by 75.216.170.236 (talk • contribs) 14 January 2010. Please sign your posts with ~ !
 * There are free wiki hosting services. For example http://www.wikia.com, which is based on MediaWiki. These are really simple. No PHP editing, no extra extensions are required. You just fill in a web form. See http://www.wikimatrix.org for a comparison of different options. Mange01 18:23, 24 January 2010 (UTC)

rPath links broken?
I can't find the information on the rPath product. After you follow the link from this Wiki page you get some info but the links on that page are broken. Does anyone have any other ideas on appliances to help with process of installing Media Wiki?

—The preceding unsigned comment was added by 173.152.84.144 (talk • contribs) 4 February 2010. Please sign your posts with ~ !
 * It seems to work now.Mange01 08:50, 25 March 2010 (UTC)

VirtualBox vs. VMware
Is one better than the other, as far as running MediaWiki is concerned? What are the pros and cons? Tisane 04:33, 16 March 2010 (UTC)

Hardware Appliance
Hi,

My friend and I were dissatisfied with the lack of an easy hardware appliance for mediawiki. So we built one ourselves and released the source code and are selling boxes to friends. Our "InnoBox" as we call it boots a working mediawiki, with a handful of popular extensions and a custom GUI to handle nightly backups and restore. I think people will find it useful. Is this the appropriate place for a link? We are selling hardware ($599) at http://innoboxdevices.com and we have released source under the AGPL at http://github.com/innobox

I assume that since TurnKey Linux is also a for-profit institution and is listed here, it should not be a problem to add one more listing, but I would like to make sure.

Best, Kramer

--- Since I didn't get a response here for the past few days, I am going to go ahead and post the link. Just let me know if you'd like it removed. --Kramer 13:22, 26 October 2010 (UTC)

Red Hat / Oracle
I'm running an Oracle 11g RAC (Real Application Cluster) on Linux and I want to start a wiki-like website on it. Is there a software bundle (or version of MediaWiki) for Oracle 11g RACs? (First of all, how can I configure it as a Web server?)

Thanks,

The Doctahedron, 16:05, 24 December 2011 (UTC)

Outdated
This page seems largely outdated, yet it's linked from Manual:FAQ. Packages in the repositories are relevant and should be updated (after hexmode, Platonides etc. manage to get the repos themselves up to date); I'm not sure about the rest. Also, isn't the title a bit confusing, given the extension bundles in the main tarball and other Tarballs? --Nemo 00:20, 21 January 2013 (UTC)

Notes from Developer Summit 2015
These are the minutes from a session on distribution of MediaWiki. --Mglaser (talk) 14:39, 3 February 2015 (UTC)

MediaWiki distribution
 * Task: https://phabricator.wikimedia.org/T86559
 * MediaWiki needs a product manager: https://phabricator.wikimedia.org/T87655

NOTES

Tarball gets you basic MediaWiki system, but not:
 * math
 * pdf render
 * VE

Future: more complicated
 * services (Parsoid, Elasticsearch, ...)

Options:
 * php-only install
 * complex setup with instructions
 * central provisioning of services
 * Automated setup using Vagrant or Puppet

MediaWiki should be seen as multiple layers:
 * 1) Extensions
 * 2) MediaWiki core
 * 3) Services (Puppet, Elasticsearch, Parsoid)
 * 4) Server, operating system, environment, ... (Docker, Vagrant)

Challenges:
 * Very different setups with different e.g. extensions
 * Upgrading becomes much more complex with multiple services
 * is an easy setup for third parties something we want?
 * What kind of setups we want to support in the future?
 * --> third parties needs clarity about what the foundation want

SCRATCHPAD

Other possible options: Prices of virtual hosts are very cheap:
 * CoreOS style containerisation of services
 * CoreOS not even necessary. Primarily setting up Docker images
 * Yeah, but CoreOS helps with the job of joining them together and managing them - non-trivial when you move from one service to lots.
 * Definitely.
 * Use an absraction layer like https://packer.io/ to separate the "virtualization" layer from the "appliance specification".
 * Have install be puppet-based, and support docker/vagrant as additional conveniences: e.g. use Ubuntu base image w/ puppet installed, and use our typical manifests to install mediawiki (and extensions) in the image.
 * Make "stable" MediaWiki-Vagrant tags/releases; add roles more tuned for deployment to cloud providers and live hosting
 * Do we want, that all people need shell access (stil without root, there are persons, that shouldn't have shell access, bc of missing knowledge about the operating system)
 * Even MediaWiki-Vagrant wants 1.5G to setup the VM

Opinion about shared hosts (Subbu):
 * I think in a lot of scenarios, shared hosting setups are better served by wiki farms that deal with upgrades and other headaches. Most of the time, these users install a software and don't / cannot handle upgrades and updates. I think we are doing these users a disservice in some way because of that. If this is about free knowledge, open knowledge, then what is needed is some company / org that is devoted to providing a dedicated mediawiki hosting service that handles all these hassles for them. I will readily drive multiple customers from India to such a business. I am done managing their disparate websites for them, for ex.
 * On most wikifarms you can not do all the things you can do, if you host your own wiki on a shared host, e.g. extension setup or something else.
 * Yes, but sticking to my experience helping folks set up CMSes .. most of them wouldn't worry about extensions.