Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
blocks:server:tweaks [2019-04-29 09:02] admin Added note on installing chromium-codecs-ffmpeg |
blocks:server:tweaks [2023-03-14 20:58] (current) mattias [Removing Unifi Wifi Support] |
||
---|---|---|---|
Line 3: | Line 3: | ||
PIXILAB regularly revisits and improves the Linux server image, resulting in newer releases. The release is indicated by the date shown as part of the filename. However, for a running installation, | PIXILAB regularly revisits and improves the Linux server image, resulting in newer releases. The release is indicated by the date shown as part of the filename. However, for a running installation, | ||
+ | This article describes how to update server images based on Ubuntu 18. If you're using server image version 200525 or later, based on Ubuntu 20, most of what's described below is already been taken care of. However, you may still want to update your operating system from time to time to keep up-to-date with security patches. | ||
- | ===== Linux Operating System Updates ===== | + | :!: If you're using an older version of server, based on Ubuntu 16, released before 2019-05-28, first follow [[blocks: |
+ | |||
+ | ===== Operating System Updates ===== | ||
System components are updated regularly. Most updates are not related to Blocks at all, and make no difference. But occasionally, | System components are updated regularly. Most updates are not related to Blocks at all, and make no difference. But occasionally, | ||
- | To update your server: | + | |
- | + | - Switch to the pixi-admin user (password is " | |
- | | + | |
- | - Switch to the pixi-admin user. | + | |
- Click the orange " | - Click the orange " | ||
- Select the " | - Select the " | ||
- If you see "OS updates", | - If you see "OS updates", | ||
+ | - Restart the server to make the updates take effect. | ||
- | {{ : | + | ===== Update Java ===== |
- | Finally, restart the server to make the updates take effect. | + | Blocks 4.1 and later uses a newer version of Java. If your server |
- | + | ||
- | :!: While most updates are for the better (or at least neutral), they may occasionally cause problems. Make sure to test all important system functions after updating | + | |
- | + | ||
- | + | ||
- | ===== Updating | + | |
- | + | ||
- | To update the Blocks program itself, follow the instructions given [[: | + | |
- | + | ||
- | ===== Installing the Chromium Browser ===== | + | |
- | + | ||
- | In preparation for Blocks 3, we're strongly recommending | + | |
- | + | ||
- | To install Chromium on your Linux-based Blocks server: | + | |
- Switch to the pixi-admin user. | - Switch to the pixi-admin user. | ||
- | - Open a terminal window. | + | - Open a terminal window |
- | - Install Chromium using the following commands: | + | - Copy and paste the following commands |
< | < | ||
- | sudo apt install | + | sudo apt-get update |
- | sudo apt install | + | sudo apt-get |
+ | sudo wget -O - https:// | ||
+ | sudo echo "deb [signed-by=/ | ||
+ | sudo apt-get update | ||
+ | sudo apt-get | ||
</ | </ | ||
- | :!: If you plan on using the browser installed on your server to edit content in Blocks, you need to install Google Chrome instead of Chromium. However, we don't recommend using the server for editing purposes. | + | Enter the pixi-admin user's password when requested. Then switch to Java 11 using the following |
- | + | ||
- | You can now remove Firefox, as Chrome/ | + | |
< | < | ||
- | sudo apt-get remove | + | sudo update-alternatives |
</ | </ | ||
- | After finishing installing/ | + | When prompted, type the number corresponding to " |
- | - Switch back to the pixi-server user. | + | Finally, verify that Java 11 is now selected: |
- | - Launch Chromium/ | + | |
- | - Once it appears in the launcher (dock) on the side, right-click the icon and chose "Lock to launcher" | + | |
- | ===== Updating the Start and Stop scripts ===== | + | |
- | The way the Blocks server is started and stopped has been enhanced a few times. This is done by two scripts located in the home folder of the "pixi-server" | + | < |
+ | java -version | ||
+ | </ | ||
- | - Download {{ : | + | The output should indicate " |
- | - Move the TAR file to your Linux Blocks server. | + | |
- | - Double click the TAR file on the Linux server. | + | |
- | - Select both files and drag them to the home folder of the pixi-server user. | + | |
- | {{ : | + | ==== Offline Procedure ==== |
- | :!: To use these scripts to start and stop the server, you must be running Blocks 2.3 or later. | + | If your Linux-based Blocks server doesn' |
- | Once installed, you can start and stop Blocks in either of the following | + | - On a computer with internet access, open a web browser |
+ | - Doing so shows a list of files. If you receive an error message, the offline files may have been moved, in which case a google search for " | ||
+ | - Download the file named temurin-11-jdk_11.0.15.0.0+10_amd64.deb, | ||
+ | - Move the downloaded deb file using a USB stick to your Blocks | ||
+ | - On your Blocks server, log in as the pixi-admin user. | ||
+ | - Open a terminal window and type the following | ||
- | * By restarting the server, which always launches Blocks. | + | < |
- | * Start using the PIXILAB Blocks icon in the task bar on the left hand side. | + | sudo apt install |
- | * Stop the server by clicking the Quit button in the Blocks window (not available if started from a non-GUI session – see below). | + | </ |
- | * Using the start.sh and stop.sh shell scripts from a terminal or SSH session. | + | |
- | The advantage with the last option is that you can start/ | + | Make sure there' |
- | :!: No Blocks | + | ===== Updating |
- | ===== Reducing the Wear on the SSD ===== | + | To update the Blocks |
- | + | ||
- | During normal operation of Blocks, most disk accesses will be READ operations used to serve media and other data to the display spots. However, due to the default behavior of most Unix-based operating systems, such accesses may still incur a write operation to update the "last accessed" | + | |
- | + | ||
- | Fortunately, | + | |
- | + | ||
- | {{ :blocks: | + | |
- | + | ||
- | Click the //Disks// icon, opening a window like the one shown below. Click the large center partition of the disk to select it. Then choose "Edit Mount Options…" | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | At the beginning of the "mount options" | + | |
- | + | ||
- | < | + | |
- | noatime, | + | |
- | </ | + | |
- | + | ||
- | :!: IMPORTANT: Note that there must be a comma separating the word //noatime// from the word //errors// that was already there. | + | |
- | The result will look like this screenshot. | ||
- | {{ : | ||
- | Click OK to save your changes, then restart the server to make your changes take effect. |