Chapter 2. Server Installation

Table of Contents

2.1. Step 1 - System Requirements
2.2. Step 2 - Create System Account
2.3. Step 3 - Configure CUPS and Samba
2.3.1. CUPS Remote Printer Browsing
2.3.2. CUPS Job History
2.3.3. CUPS Job ID
2.3.4. CUPS Job Privacy
2.3.5. CUPS Web Interface
2.3.6. CUPS security fix
2.3.7. CUPS systemd service
2.3.8. Test CUPS
2.4. Step 4 - Optional System Settings
2.4.1. Set Default Paper Size
2.5. Step 5 - Check Firewall Settings
2.6. Step 6 - Download and Install
2.7. Step 7 - Save Encryption Keys
2.8. Step 8 - Configure
2.8.1. Step 1 - Login
2.8.2. Step 2 - Change Admin Password
2.8.3. Step 3 - Set Locale
2.8.4. Step 4 - Set Currency Code
2.8.5. Step 5 - Set User Source
2.8.6. Step 6 - User Synchronization
2.8.7. Step 7 - Set Mail Options
2.8.8. Step 8 - Set Driverless File Transfer Print
2.9. Step 9 - Share SavaPage Client Files
2.10. Step 10 - Testing
2.11. What's next?

This chapter covers the initial installation and configuration of SavaPage in your network environment.

Initial installation takes only a few minutes on a prepared server. This guide will walk you through installation and configuration step-by-step. The process is summarized below:

  1. System requirements check.

  2. Downloading and installing SavaPage.

  3. Completing the configuration.

  4. Testing the software.

Tip

If you would like to know the technical details behind the SavaPage installer, take a look at Section 13.1, “The Installation Process”.

Important

By installing the program, you are accepting and agreeing to the terms of the GNU Affero General Public License (AGPL). Please review Appendix P, GNU Affero General Public License (AGPL) before continuing.

2.1. Step 1 - System Requirements

Before proceeding with the installation you should take a few moments to verify system requirements. Is the operating system version supported and are patches up-to-date? Take a few minutes to verify the system is current and supported (see Section 1.2, “System Requirements”).

The SavaPage installation program needs the commands which, strings, gunzip and perl. So, make sure the binutils, debianutils (for Debian based systems), perl and gzip packages are installed.