-
Notifications
You must be signed in to change notification settings - Fork 34
Installation
This page will guide you through the steps required to install Wavelog onto a Linux web server that is using the LAMP stack (that's Linux, Apache, MySQL, and PHP). The specifics of your server setup can be largely up to you as there are various Linux distributions, for example. This guide will focus on Debian / Ubuntu so instructions given here may not apply to other distributions.
-
Any modern Linux installation capable of supporting the other prerequisities.
- Recommended:
- Debian 11 or 12
- Ubuntu 22.04
-
Web server (e.g. Apache >= 2.4 or nginx)
-
- InnoDB has to be available and set as default engine
-
PHP <= 8.2 plus modules (8.3 seems to work without issues):
- php-curl
- php-mbstring
- php-mysql
- php-xml
- php-zip
Installing a suitable operating system, database server and web server are tasks that are outside the scope of this guide but there are plenty of resources to help you get started. Have a look at these guides from DigitalOcean to set up either Debian or Ubuntu LTS.
Once you have your LAMP stack installed, make sure that the required PHP modules are available as not all will be installed by default:
sudo apt install php-curl php-mysql php-mbstring php-xml php-zip
If you use Apache2 as Webserver you maybe need aswell
sudo apt install libapache2-mod-php
Use php -v
to check the installed version. Minimum Version is PHP 7.4
Note
If you use nginx as web server you will need to make sure that the PHP handler does serve .php correctly and not only if the address ends on .php
. See this issue. The basic change in the config is (remove the dollar sign):
# pass PHP scripts to FastCGI server
#
- location ~ \.php$ {
+ location ~ \.php {
For ease of installation and updating, it's recommended to acquire the Wavelog application files using Git. Git is most likely installed already on your Linux distribution. If not, use sudo apt-get install git
to obtain it.
The git clone
command is used to fetch the latest build of Wavelog from the repository on GitHub. This command downloads the application files in their current state on the master branch:
git clone https://github.com/wavelog/Wavelog.git [output_directory]
Replace output_directory with the full path to the directory where you'd like the application files to be created locally (don't include the square brackets). For example, if you configured Apache with a site that uses _/var/www/html as its DocumentRoot directory then the command becomes
git clone https://github.com/wavelog/Wavelog.git /var/www/html
Have a look at the Webserver Configurations for more information on site configuration.
During normal operation, Wavelog will need to write to certain files and directories within the root Wavelog directory (i.e. where you extracted the files in the previous step). You'll need to set the permissions and ownership on these directories appropriately.
The following folders need to be writable by PHP:
- /application/config/
- /application/logs/
- /backup/
- /updates/
- /uploads/
- /images/eqsl_card_images/
/var/www/html
in the below command with the appropriate directory if you cloned the Git repository somewhere else in the previous step!
Set the basic permissions (work in most cases). Don't forget to adjust the directory:
directory=/var/www/html
sudo chown -R www-data:www-data $directory
sudo find $directory -type d -exec chmod 755 {} \;
sudo find $directory -type f -exec chmod 664 {} \;
These permissions may differ on your setup!
Wavelog needs a MySQL database to store application and user settings, along with user data such as logbooks.
The basic steps for creating a blank database are very similar for both MySQL and MariaDB - we'll cover those here - but the specific steps relating to securing your database and server will differ. As with the Apache configuration, those latter steps are outside the scope of this guide but you can refer to the MariaDB documentation or the MySQL documentation as a starting point.
Let's start by using the mysql
command to connect as the root user. If your server is already configured for something else then you may have another user configured with the ability to create databases - you can substitute that username if so. Read more about connecting with the mysql
client in the MySQL documentation.
sudo mysql -u root -p
Note: The mysql
tool has the same name in both the MySQL and MariaDB packages.
Now issue the following command to create a database for Wavelog, replacing db_name
with a name of your choice, e.g. wavelog
. Note this name down as you'll need it later for the Wavelog install wizard.
CREATE DATABASE db_name;
Next, create a user and grant it privileges on the Wavelog database. Creating a new user is optional if you already have a valid non-root user on the MySQL/MariaDB server. Remember to again replace db_name
with the name you chose previously for the database, user1
with the name of the user (e.g. waveloguser
) to create and password1
with a real, strong password! Keep the username and password safe as you'll need these for the Wavelog installer later.
CREATE USER 'user1'@localhost IDENTIFIED BY 'password1';
GRANT ALL PRIVILEGES ON db_name.* TO 'user1'@'localhost';
QUIT
You need to run the installer. At this point, please open <url-to-wavelog>/install
and follow the guide.
- If you want to know if the person you're working uses LoTW, run:
https://<URL-To-Wavelog>/index.php/update/lotw_users
. This is the initial run, but we'll run this every week from cron momentarily.
You can use cron jobs to automate some of the regular Wavelog maintenance tasks. See Recommended Cron Jobs and Cronmanager for instructions.
After your first login you have to set up some things in Wavelog. Just follow the warnings on the dashboard.
- Installation on Linux server
- Installation on Windows server
- Installation via Docker
- Updating Wavelog
- Hints & Tips
- wavelog.php Config
- Migrate Cloudlog to Wavelog
- Authentication
- QSO Modes
- Backup
- Update Country Files
- User Accounts
- Global Options
- Debug
- Maintenance Mode
- Recommended Setup for Special Callsigns and Clubs
- API
- Station Profiles
- Radio Interface
- ADIF Import / Export
- Logbook of The World
- eQSL
- Print Requested QSLs
- Clublog Upload
- QRZ Logbook
- KML Export