![]() ![]() That would look something like this: chown www-data:www-data /var/www/whatever-folderīottom line is though that this probably won't make a huge difference, it's just better practice IMO In step 3, I'd sugggest that rather than chmod 777 (giving all users read/write/execute) you instead give ownership of the directories to www-data (the webserver user account). You can skip step 2 (as you don't need to upload files). then you can do it all from there (as in step 1 in those instructions). via wget command) and then unzip (as described in install docs). If you download Mediawiki software from the commandline (i.e. If you are unfamiliar with MySQL then I suggest that you use phpMyAdmin (A MySQL WebUI that comes with TKL, it is accessable via https::12322) Because you are creating a new install you may need to create a MySQL DB and Mediawiki user. Yes pretty much (although you can start from step 1 - you don't need to install Apache, MySQL and PHP as they are all there in LAMP). So assuming that you follow my suggestion (and start with a LAMP appliance) then the answers to your questions are: Whereas if you restore to a Mediawiki appliance it will require tweaking and mucking around to get it all working again. This will make your backup larger, but will also mean that if you restore your backup (to a new TKL LAMP server) then it will work OOTB. The logic behind that suggestion is that if you use the LAMP appliance then iwhen you do a backup with TKLBAM all the Mediawiki files will also be included. These aren't issues.īut the other thing I would consider if I were you would be to start with the LAMP appliance rather than the Mediawiki one. I understand that going "upstream" means more maintenance time and potential security risks if I fail to update. I'd like to first set-up 1 MediaWiki server, take a snapshot of that, and then use it for the second one. In relation to #2, have there been any changes over the last two years (since the time of writing for the post I linked), where someone can install the default mediawiki appliance and then upgrade through the command line? tar.gz to the server and *then* perform the necessary operations? Is there a way of installing the entire thing over the command line or do I have to upload the. ![]() I think those are still present on the server as I only removed the mediawiki appliance. I just need a few pointers in the right direction:ĭoes installing the latest MediaWiki version from scratch on a TLK server imply I have to follow every single step listed here: (?) For example I don't know whether I'd have to mess around with MySQL. There's a few questions I have in this regard which I was hoping someone could help me out with. I have zero experience with managing servers from a command line-and my command line knowledge is very limited in the first place. The main thing I'm concerned about is installing it in the most efficient way possible. I now need to install from the upstream and this is where I'm unsure on what next step to take. With no data no backup, I decided to proceed with removing the mediawiki 1.15 appliance using: (note that I'd like to upgrade to 1.21.2) I did a search on how to upgrade and came across this thread. However, I realised the version installed (1.15) is incompatible with the extensions I need (such as Semantic Wiki, which requires at least 1.17). This worked like a charm, no problems there. So far I have started a micro server using the free usage tier and selected the mediawiki applicance to be installed. I'm a new user to Turnkey Linux and I'm interested in starting 2 MediaWiki servers that are running the latest version of the MediaWiki software. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |