Difference between revisions of "Wikirestore"

From Cybagora
Jump to: navigation, search
(Created page with "This page describes the work I need to accomplish and I need help for. . == <br/>Approach == My background is not software development (I am more network software and intern...")
 
Line 2: Line 2:
  
 
.
 
.
== <br/>Approach ==
+
==<br/> Background ==
  
My background is not software development (I am more network software and internet architecture oriented). I have experience in an odd method inherited from learning developping in extending the QNX OS for a personal venture.
+
I work on Windows to manage hosting under Linux, developping Linux script generators on Windows. I find this convenient to better understand how to keep things simple and see the systemic flaws.
  
* I want to understand the Linux machine I use and the scripts necessary to execute what I want.
+
=== <br/> Linux ===
* I work on windows (often DOS, I am an old one) where I have my tools [I learned it helped spotting flaws more easily to work in two different contexts] in order to :
+
I use to use mediawiki as a working tool at a Centos hosting.  
** build a database (excel) of the parameters I need for the different sites I micro-industrialize.
+
** develop in "rusty" C (I am an old one) program to general a systematic script system.
+
** load/maintain a copy of the scripts on the remote Linux machine and cron/execute it to carry the tasks on many sites.
+
  
I managed this way several projects with up to 3000 similar sites. I hate non-prompt relation with the machine.
+
I first built them in:
 +
* downloading a MediaWiki and some extensions on my Windows machine,
 +
* uploading them each time I created a new site,
 +
* initiating a MySQL database on the site cPanel,
 +
* running the php installation file,
 +
* downloading the LocalSetting.php file on my Windows machine for back-up and adding access protection lines
 +
* reloading it on the Centos machine.
  
=== <br/>The kind of help I need ===
+
Then I started creating them with Softaculous.
  
I need '''models''' of the scripts for the task I have in mind in my above context, and support (explanation) if I meet difficulties with them and my approach. I know I have to use MySQL/PHP because most of the tools use them. But I do not know MySQL (never found a MySQL '''system management''' doc) and I have not developped PHP for years. I try to stay with batch/scripts I can generate.  
+
My hosting company transferred me to a dedicated machine for more control under WHM+cPanel.  
  
I am more interested in learning possibly Python, certainly JS and Elixir and NoSQL (CouchDB?) in a structured way, but did not find yet a good method/teacher for that.
+
This became more complex when PHP, then MySQL were to be updated for all sites. Mediawiki people explained me the problem. I want to come back to my initial system but in using a single mediawiki copy, virtual directories, a MySQL creation script.
  
==<br> Wiki project ==
+
The target is to create, support, and keep updated the environment of hundreds of wiki sites.
  
I have became found of Wikis and want to expand the concept from experiencing first MediaWiki simple, robust, versatile, etc. farming for my own need. I plan to document further on a simple MediaWiki oriented use by people for people (cyberagora). Then to switch the wiki support to a NoSQL + DNS like environment. But this is '''NOT''' for now.
 
  
===<br/> Background ===
+
=== <br/>Local XAMPP (Windows) ===
  
I use to use mediawiki as a working tool on a Centos hosting company. Initially I built them in downloading a MediaWiki and some extensions on my Windows machine, uploading them each time I created a new site, initiating a MySQL database on the site cPanel, running the php installation file, downloading the LocalSetting.php file on my Windows machine for back-up and adding access protection line and reloading it on the Centos machine.
+
I started using mediawiki as well on my local windows machines. I installed XAMPP and the mediawiki files in a dropbox directory. I run these wikis with SQLight. It works well on my three dropbox coupled machines.
  
Then I started creating them with Softaculous.
+
== <br/>What I want to achieve ==
  
My hosting company transferred me to a dedicated machine for more control under WHM+cPanel. This became more complex when PHP was to be updated. Then MySQL to get consistent with a new Softaculous release. As a result I cannot access the displayed pages of my older sites (I can access the edit). Mediawiki people explained me it is only a question of reload with the appropriate versions.
+
I want to stabilize
 +
* an operational "face" of my wikis on a new "Linux VM" host without WHM/cPanel like stuff
 +
* and a back-office (backup, development, testing, etc.) on the Windows machines.
  
=== <br/>Local XAMPP (Windows) ===
+
=== <br/>The help I need ===
  
I started using mediawiki as well on my local windows machines. I installed XAMPP in a dropbox directory as well as mediawiki running it with SQLight. It works well on my three dropbox coupled machines.
+
I only need '''models''' of the scripts for the task I have in mind in the MySQL context I ignore the administration, and support (explanation) if I meet difficulties with them and my approach.
  
=== <br/>Current situation ===
+
This probably calls for an initial mail exchange followed by occasional exchanges on the way to proceed for some tasks in my context.
  
I have written scripts (may be to review) to build a "/jfc" directory on my Centos machine where I backup my wiki as:
+
=== <br/>Current situation on the Centos Machine ===
  
 +
I have written scripts (may be to review) to build a "/jfc" directory on my Centos machine where I backup my wiki as:
 
* "name of the wiki".lsp for the LocalSetting.php file
 
* "name of the wiki".lsp for the LocalSetting.php file
 
* "name of the wiki".sql for the QSL dump
 
* "name of the wiki".sql for the QSL dump
 
* "name of the wiki".xml for the XML dump.
 
* "name of the wiki".xml for the XML dump.
* "images" directory
 
  
Then I downloaded that files to my windows machine and organized them  
+
=== <br/> situation on the windows machine ===
 +
 
 +
I downloaded that files to my windows machine and organized them as:
  
 
* \dropbox\jfc\"name of the wiki"/LocalSetting.php for the LocalSetting.php file
 
* \dropbox\jfc\"name of the wiki"/LocalSetting.php for the LocalSetting.php file
Line 51: Line 57:
 
* \dropbox\jfc\"name of the wiki"/"name of the wiki".xml for the XML dump.
 
* \dropbox\jfc\"name of the wiki"/"name of the wiki".xml for the XML dump.
 
* \dropbox\jfc\"name of the wiki"/"images" for the files loaded on the wikis (for the time being, no script)
 
* \dropbox\jfc\"name of the wiki"/"images" for the files loaded on the wikis (for the time being, no script)
 +
* \dropbox\ediwki\wikicurr for a copy of the current mediawiki releads (1226)
 +
* \dropbox\xampp standard set-up with htdocs, mysql\bin.
  
== <br/>What I want to achieve ==
+
The local wikis are to be at \dropbox\xampp\htdocs\wiki\"name of the wiki"
  
I want to have an operational face on the Linux host side and a back-office (backup, development, testing, etc.) on the Windows side.
+
 
 +
== <br/>The help I need ==
  
 
=== <br/> on the windows side ===
 
=== <br/> on the windows side ===
Line 61: Line 70:
  
 
* understand how to and set-up a password from \dropbox\xampp\mysql\bin  
 
* understand how to and set-up a password from \dropbox\xampp\mysql\bin  
* load a copy of the wikis database
+
* load a copy of a wiki database in MySQL
 +
* the model of batch file to automate the database load (or reload)
  
 
'''2. Wiki'''
 
'''2. Wiki'''
  
* set-up virtual directories (Windows junction?) in \dropbox\xampp\htdocs\wiki
+
* set-up wiki virtual directories in \dropbox\xampp\htdocs\wiki from "\dropbox\ediwki\wikicurr"
** for the \dropbox\jfc\"name of the wiki"\LocalSetting.php file and the "images" directory.
+
* where I will copy the "...wiki\"name of the wiki"\LocalSetting.php" file and the "images" directory.
** for the \dropbox\ediwki\wikicurr where I intend to keep a copy of the current mediawiki release.
+
 
  
 
===<br/> on the host side ===
 
===<br/> on the host side ===
  
'''1. install a new VM'''
+
'''1. install a new "Linux VM"'''
  
 
* this machine should be dedicated to Wikis + Mails + Mailing lists + DNS in a first time.
 
* this machine should be dedicated to Wikis + Mails + Mailing lists + DNS in a first time.
* it should use no WHM/cPanel etc. only password, config files, scripts and cron so I can replicate it easily.
+
* it should support standard XAMPP config, files, scripts and cron  
 +
** I can replicate easily from scripts in one single script directory when creating, updating, maintaing them
 +
** in symbiosis with the windows side (I suspect the scripts may differ but metaparameters will be the same).
  
 
'''2. load it'''
 
'''2. load it'''
  
* same process as under windows. I load the database, the LocalSettings.php, "images" files and appropriate scripts.
+
* same process as under windows from existing Linux machine, but under "Linux VM" from windows.
* I run the appropriate scripts.
+

Revision as of 09:39, 11 June 2014

This page describes the work I need to accomplish and I need help for.

.


Background

I work on Windows to manage hosting under Linux, developping Linux script generators on Windows. I find this convenient to better understand how to keep things simple and see the systemic flaws.


Linux

I use to use mediawiki as a working tool at a Centos hosting.

I first built them in:

  • downloading a MediaWiki and some extensions on my Windows machine,
  • uploading them each time I created a new site,
  • initiating a MySQL database on the site cPanel,
  • running the php installation file,
  • downloading the LocalSetting.php file on my Windows machine for back-up and adding access protection lines
  • reloading it on the Centos machine.

Then I started creating them with Softaculous.

My hosting company transferred me to a dedicated machine for more control under WHM+cPanel.

This became more complex when PHP, then MySQL were to be updated for all sites. Mediawiki people explained me the problem. I want to come back to my initial system but in using a single mediawiki copy, virtual directories, a MySQL creation script.

The target is to create, support, and keep updated the environment of hundreds of wiki sites.



Local XAMPP (Windows)

I started using mediawiki as well on my local windows machines. I installed XAMPP and the mediawiki files in a dropbox directory. I run these wikis with SQLight. It works well on my three dropbox coupled machines.


What I want to achieve

I want to stabilize

  • an operational "face" of my wikis on a new "Linux VM" host without WHM/cPanel like stuff
  • and a back-office (backup, development, testing, etc.) on the Windows machines.


The help I need

I only need models of the scripts for the task I have in mind in the MySQL context I ignore the administration, and support (explanation) if I meet difficulties with them and my approach.

This probably calls for an initial mail exchange followed by occasional exchanges on the way to proceed for some tasks in my context.


Current situation on the Centos Machine

I have written scripts (may be to review) to build a "/jfc" directory on my Centos machine where I backup my wiki as:

  • "name of the wiki".lsp for the LocalSetting.php file
  • "name of the wiki".sql for the QSL dump
  • "name of the wiki".xml for the XML dump.


situation on the windows machine

I downloaded that files to my windows machine and organized them as:

  • \dropbox\jfc\"name of the wiki"/LocalSetting.php for the LocalSetting.php file
  • \dropbox\jfc\"name of the wiki"/"name of the wiki".sql for the QSL dump
  • \dropbox\jfc\"name of the wiki"/"name of the wiki".xml for the XML dump.
  • \dropbox\jfc\"name of the wiki"/"images" for the files loaded on the wikis (for the time being, no script)
  • \dropbox\ediwki\wikicurr for a copy of the current mediawiki releads (1226)
  • \dropbox\xampp standard set-up with htdocs, mysql\bin.

The local wikis are to be at \dropbox\xampp\htdocs\wiki\"name of the wiki"



The help I need


on the windows side

1. MySQL

  • understand how to and set-up a password from \dropbox\xampp\mysql\bin
  • load a copy of a wiki database in MySQL
  • the model of batch file to automate the database load (or reload)

2. Wiki

  • set-up wiki virtual directories in \dropbox\xampp\htdocs\wiki from "\dropbox\ediwki\wikicurr"
  • where I will copy the "...wiki\"name of the wiki"\LocalSetting.php" file and the "images" directory.



on the host side

1. install a new "Linux VM"

  • this machine should be dedicated to Wikis + Mails + Mailing lists + DNS in a first time.
  • it should support standard XAMPP config, files, scripts and cron
    • I can replicate easily from scripts in one single script directory when creating, updating, maintaing them
    • in symbiosis with the windows side (I suspect the scripts may differ but metaparameters will be the same).

2. load it

  • same process as under windows from existing Linux machine, but under "Linux VM" from windows.