Installer

[Arrow768]

Intro

Add a installer to the Webpanel, that helps with the initial setup of the WebPanel and the Store Plugin

It should check if:

• The requirements are fulfilled
• The chmod is set correctly (uploads folder, settings folder)
• The webpanel db exists and import the db if it doesnt
  • It imports the webpanel db without checking first if its already imported.
  • It doesnt matter because it just drops the webpanel tables and reimports them afterwards if they already exist
• The store database exists and inform the user if it doesnt
• Force a change of the admin password
  • This could be resolved via a check in the authcontroller for the password: password
• It should create a INSTALLED file when the installation is finished and allow only another run if the file is deleted
  • The database.php is used for that

The following procedure has been suggested by @Drixevel :

• Download/Install webpanel onto a webserver and go through an installation setup similar to forum softwares.
• Install the SQL database entries from there then offer basic instructions on where to install the store main plugin modules & item modules, etc.
• Then they download the plugins from there and install each of those on the servers and you give them an example database config entry they can add to their database.cfg files similar to Sourcebans and how it does it.

Solves #16

[Shigbeard]

By requirements, you do also mean ensuring the software isn't already installed?

Security, ofc.

[Arrow768]

By requirements, I mean the requirements listed in the Wiki

The first version of the installer is only intendet for the initial setup.
Updating might be covered by #25

[Shigbeard]

Fair enough. I was more thinking how can you prevent an unauthorized user to install over the existing package in an attempt to circumvent passwords etc.

[Arrow768]

A installer for the old webpanel is unlikely to happen.
The new webpanel can be installed by running 3 cli commands and editing a config file

[Shigbeard]

That still seems highly advanced and unnecessary. You can do it all in a single file with many functions and a basic GUI, navigated using $_GET or $_POST on submission of details such as "MySQL", etc.

[Arrow768]

It already works in the new webpanel.
So I dont see a need to add a installer in the old webpanel (which wont be further developed when the new webpanel is stable).
But if you create a merge request with a working installer, I am happy to merge it.

[Shigbeard]

I'll create one. Any particular directory you would prefer? In the end, if the script isn't installed correctly and a user browses to the index page, it will prompt for installation. I can also make it ensure only authorized users initiate installation.

[Arrow768]

Feel free to create / modify the files / folders you need to implement the installer.

About the authorized user:
I think it would be enough if the first question of the installer is the question for the db credentials.
Only the admin can answer the question.
Once it installer is finished it should lock itself out.
(Maybe by creating a installed file thats checked for when running the installer ?)

[Shigbeard]

Hmm, ok. An installed file sounds fine.

[Shigbeard]

Did a bit of thinking about that installed file. I could get away with just using the database.php file that you are supposed to rename from database.sample.php. The implication there is that by having that file there, the software is considered "installed" and ready for use. If for some reason you need to re-install, deleting or editing that file would logically be involved in that process.

Plus the installer would create it from the sample file anyway.

[Shigbeard]

DONE