moodLearning Wiki


This shows you the differences between two versions of the page.

Link to this comparison view

ubuntu-server-setup [2018/11/14 17:12]
ubuntu-server-setup [2020/06/13 23:10]
Line 1: Line 1:
-====== eLibrary installation on Ubuntu server ====== 
-===== Ubuntu 18 ===== 
-  * create a bootable USB using an [[http://​​ubuntu/​releases/​18.04/​release/​|Ubuntu 18 image]] and [[https://​​|Etcher]]. ([[https://​​tutorial/​tutorial-create-a-usb-stick-on-macos#​0|Mac guide here]]) 
-  * install Ubuntu 18 server using the bootable USB (Tips: erase partition of original disk, format one whole drive, provide enough swap) 
-  * install Ubuntu 18 desktop (the server will double as workstation for library management purposes) 
-  apt install lightdm</​code>​ 
-  * install Eprints using the //deb// approach from  [[https://​​w/​Installing_EPrints_on_Debian/​Ubuntu|these instructions]]. [[https://​​watch?​v=PtgVytIcG54|This youtube video]] can help visualise the installation process. 
-Some crucial steps include: 
-  * getting root access right by running //​mysql_secure_installation//​ setting this up: 
-CREATE USER '​eprints'​@'​localhost'​ IDENTIFIED by '​changeme';​ 
-GRANT ALL PRIVILEGES ON *.* TO '​eprints'​@'​localhost'​ WITH GRANT OPTION; 
-  * running //epadmin create//, up to where it says: 
-Database Superuser Username [root] ? 
-where you'll input "​eprints"​ (not "​root"​) as set above in your mysql setup. 
-===== Ubuntu 14 ===== 
-  * install a linux server/​desktop (in this example, Ubuntu 14.04 or some LTS version is assumed) 
-  * mod /etc/hosts to include your made-up domain ( to point just to itself ( 
-  * use [[http://​​unimaswiki/​bin/​view/​HOW-TO,​+Tutorial+%26+User+Manual/​HOW-TO+%3A+Install+Eprints+v3.3.12++on+Ubuntu+14.04+With+LDAP+Authentication|Eprints installation guide from Unimas]]. Skip the part on LDAP authentication,​ especially if you don't imagine hundreds of people logging in to upload materials. Ordinary users can download stuff even without authentication. Also skip the https part, unless you're dealing with sensitive information and you can imagine some of your users capable of doing a man-in-the-middle attack. 
-  * mod your router'​s DHCP to provide for a **static** IP for the server (say, that's within the area of your DHCP service ​