Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
started:installation:basic_installation [2021/12/09 19:40] pdsci-admin [WinterCMS Installation] |
started:installation:basic_installation [2021/12/10 11:41] (current) pdsci-admin [WinterCMS Installation] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ====== WinterCMS Installation ====== | ====== WinterCMS Installation ====== | ||
| - | Using a (local) server or shared hosting web space. | + | Here you will find a pictured tutorial how to install WinterCMS on a (local) server or shared hosting web space. |
| + | <WRAP tip> | ||
| + | **All Steps in a Brief**\\ | ||
| + | * Download Wintercms from https:// | ||
| + | * Unzip the downloaded files and upload them to your server | ||
| + | * Start the install.html | ||
| + | * Follow the steps of the installation dialog | ||
| + | </ | ||
| + | |||
| + | |||
| + | === Additional Sources === | ||
| + | Find more information on installation on:\\ | ||
| + | * the WinterCMS homepage: https:// | ||
| + | * YouTube: [[https:// | ||
| + | * also YT: [[https:// | ||
| + | |||
| + | Because all the CLI installations require a program named composer on the server and this step is skipped on the YT tutorials mentioned above, here a link to a YT covering this step: https:// | ||
| + | |||
| + | |||
| + | Anyhow, this HowTo below will cover the Web installation. | ||
| ===== Requirements ===== | ===== Requirements ===== | ||
| **Hard- & software: | **Hard- & software: | ||
| Line 18: | Line 37: | ||
| * Some FTP or SFTP software like WinSCP or FileZilla on Windows or Mac. Not required for Linux if remote directory is mounted. | * Some FTP or SFTP software like WinSCP or FileZilla on Windows or Mac. Not required for Linux if remote directory is mounted. | ||
| * WinterCMS can be installed using either a mySQL (or some other) databases - so an empty DB has to be prepared - or via SQLlight. | * WinterCMS can be installed using either a mySQL (or some other) databases - so an empty DB has to be prepared - or via SQLlight. | ||
| - | * WinterCMS installation files as to download from the WinterCMS website on https:// | + | * WinterCMS installation files as to download from the WinterCMS website on https:// |
| For testing purposes WinterCMS can also be installed on a RaspberryPi (Version 3 or later recommended) or some NAS like QNAP or Synology. | For testing purposes WinterCMS can also be installed on a RaspberryPi (Version 3 or later recommended) or some NAS like QNAP or Synology. | ||
| ==== Step 1 Download the Installer ==== | ==== Step 1 Download the Installer ==== | ||
| - | Download the installation files from https:// | + | Download the installation files from https:// |
| On top of the installation page the requirements are listed. Just double check against your server specifications. Usually most shared hosting fits to these requirements. | On top of the installation page the requirements are listed. Just double check against your server specifications. Usually most shared hosting fits to these requirements. | ||
| Line 29: | Line 48: | ||
| {{: | {{: | ||
| - | Scrolling down there a three ways to install WinterCMS | + | Scrolling down there are offered |
| * via Web Installer (this will be covered here) | * via Web Installer (this will be covered here) | ||
| * via Composer (a special php script to install software on a server, very versatile but a little tricky) | * via Composer (a special php script to install software on a server, very versatile but a little tricky) | ||
| Line 45: | Line 64: | ||
| Here are some screenshots as an example using WinSCP\\ | Here are some screenshots as an example using WinSCP\\ | ||
| On the left side there are the unzipped installation files. | On the left side there are the unzipped installation files. | ||
| - | On the right side an empty directory (named 'octoSandbox' | + | On the right side an empty directory (named 'wncms1') as an example) is prepared. |
| {{: | {{: | ||
| Line 66: | Line 85: | ||
| {{: | {{: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| - | If these are ok proceed with the next steps.\\ | + | If these are ok, proceed with the next steps.\\ |
| - | If not follow the information provided by the Installer (ok, this may be the tricky part)\\ | + | If not, follow the information provided by the Installer (ok, this may be the tricky part)\\ |
| Next step is the Licence you have to accept. But WinterCMS is open-source (and will stay). So don't worry.\\ | Next step is the Licence you have to accept. But WinterCMS is open-source (and will stay). So don't worry.\\ | ||
| Line 73: | Line 92: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| - | ===== Set installation parameter | + | ==== Step 4 Set installation parameter ==== |
| **Now the hard work** (just kidding ;) **begins**: | **Now the hard work** (just kidding ;) **begins**: | ||
| - | At first there is a site name to set and the URL the site is located. In addition the path to the backend (wheee all the work to edit the site will be done) can be changed from the default " | + | At first there is a site name to set and the URL the site is located. In addition the path to the backend (where all the work to edit the site will be done) can be changed from the default " |
| For additional security and against too curious people it may be a good idea to change the name, but it's not that important to my experience.\\ | For additional security and against too curious people it may be a good idea to change the name, but it's not that important to my experience.\\ | ||
| Line 86: | Line 105: | ||
| Usually the hostname is " | Usually the hostname is " | ||
| - | Furthermore, | + | Furthermore, |
| {{: | {{: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| \\ | \\ | ||
| - | **Set the backend administrator**\\ | + | **Set a backend administrator**\\ |
| Next the backend administrator has to be set. Please notice: This is different from the database access. And you should use an other username and password as for the DB!\\ | Next the backend administrator has to be set. Please notice: This is different from the database access. And you should use an other username and password as for the DB!\\ | ||
| + | Once WinterCMS is installed more backend admins - with different rights - can be added to the system.\\ | ||
| {{: | {{: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| Line 109: | Line 129: | ||
| * a non empty database (just empty it, e.g. via phpMySql) | * a non empty database (just empty it, e.g. via phpMySql) | ||
| - | ==== Step 4 Start the Final Installation ==== | + | ==== Step 5 Start the Final Installation ==== |
| Usually and if all was edited properly the check will be ok and after clicking at the button " | Usually and if all was edited properly the check will be ok and after clicking at the button " | ||
| {{: | {{: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| - | If everything runs fine after installing a feedback screen is displayed giving the choice to either call a prepared website (usually called // | ||
| - | \\ | ||
| \\ | \\ | ||
| + | ==== Finally ... ==== | ||
| + | If everything runs fine after installation, | ||
| {{: | {{: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| Line 122: | Line 142: | ||
| \\ | \\ | ||
| - | ===== | ||
| Clicking the "View your install" | Clicking the "View your install" | ||
| {{: | {{: | ||
| Line 130: | Line 149: | ||
| \\ | \\ | ||
| \\ | \\ | ||
| - | Clicking the "View your Backend" | + | Clicking the "View your Backend" |
| {{: | {{: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| \\ | \\ | ||
| \\ | \\ | ||
| - | ===== Congratulations! It' moving. =====\\ | + | ===== Congratulations! It's moving. ===== |
| Finally you are rewarded with the Dashboard of the WinterCMS Backend :) \\ | Finally you are rewarded with the Dashboard of the WinterCMS Backend :) \\ | ||
| And you are free to build your webpage, blog, shop, game, webapp or whatever you like to start.\\ | And you are free to build your webpage, blog, shop, game, webapp or whatever you like to start.\\ | ||