![]() To do these things we need to run a second container, hack on php.ini and map the HTML files locally. Let’s setup a production database with it using Mariadb, configure our maximum upload size so we can upload large images (and import lots of templates) and prepare ourselves to install as many extensions as we need. Now we have MediaWiki running on port 80 and you can test this by visiting the localhost page: But we want persistence, we want our wiki to live on so let’s not just fire it up and walk away. To do so we just need a simple commmand docker run -name mediawiki -p 80:80 -d mediawiki To get started we could just run Docker’s, uh, run command to fire up a MediaWiki instance and that would be perfectly fine. Use Docker Compose with MediaWiki To Customize Your Wiki Experience Officially they have us do this with the LocalSettings.php file which will contain our settings for MediaWiki, we’ll just be taking things one step further. To do so we’ll just copy some files from the Docker container and mount them when we restart the image. There are other options like Bitnami’s image – but why stray from the official images? We can customize it to our liking without taking a performance hit which will be key. This is going to be our basis for the setup we’re going to run. To do so I suggest taking a look at the official Docker image page for Mediawiki. We suggest you start with their official instructions though I’ve covered how to install Docker in Debian 10 in another post about Mastodon. That’s right, you can host a wiki, using MediaWiki, even in a Windows 10 Docker container. Docker is just a cleaner way to try these things out – so we’re going to mark Docker as required for this project.Īgain, I don’t want to cover how to install Docker – we have assumed thus far you’re even running Linux though you don’t have to be. A fragile base system that might not get cleaned up should we decide to back out of our fun-time (maybe quarantine) project. A lot of the packages we like to discuss here on Kinda Lame are maybe not always the most complicated but they require a set of dependencies installed on your base system. We love Docker at Kinda Lame! Simply put it’s the easiest way to try out software without hosing your Linux (or Windows) install. It is the embodiment of the original world wide web dream – so let’s get started. Even in small business and corporate environments there is value in having a central data store for human knowledge and a searchable and linkable wiki is a great way to get that done. No matter the topic, fan pages, fiction or putting together a family background website – you can relatively easily and quickly start up a wiki site and start documenting whatever you’d like. And one of the coolest projects out there is the ability to self-host MediaWiki software that lets you start your own wiki site (like Wikipedia). There are too many cool projects out there to not take some time to play with and get your hands dirty. I added similar templates as migration_done and migration_discarded with the corresponding categories.Here at Kinda Lame, we like self hosting things – being in control of our own software. This uses a CSS class for tables we had been using before and adds the page to a specific category. "/api.php?action=query&list=allpages&format=json&aplimit=5000&apnamespace=100") Įcho "Fetching ' $editToken = $result->query->pages->$dash1->edittoken "/api.php?action=query&format=json&prop=info|revisions&intoken=edit&titles=Main%20Page") Throw new Exception("Login token not found in XML") I started with the loginscript from here and wrote this script: #!/usr/bin/php The Replace_Text extension was unsuccessful, so I ended writing my own script that uses the MediaWiki API. This way it should be possible to get a clean, up to date wiki without forgetting anything important. Every user should then look through the pages he is responsible for, copy the content over to the new wiki and change the template to another one marking the page as migrated (category:migration_done) or discarded (category:migration_discarded). To make this easier I want to add a textblock to the top of each existing page, specifically a template with a notice that this page hasn't been migrated or discarded yet and a category where all these pages are collected (e.g. That's why we want to start with a blank wiki and migrate the content manually, discarding and/or updating outdated pages. The content of the wiki has been migrated from an even older wiki before (where errors regarding formatting were generated), grown over time and is now outdated in large parts. I'm planning to migrate a MediaWiki over to another wiki. How do I add a text (notice) to the content (not a header or global template) of every page?
0 Comments
Leave a Reply. |