Difference between revisions of "Installing Omeka for CEDEUS"

From stgo
Jump to: navigation, search
(Setup of VM based on Ubuntu 1404 VM)
(Setup of VM based on Ubuntu 1404 VM)
Line 20: Line 20:
 
# start VM and change the computers name:
 
# start VM and change the computers name:
 
#* <code>VBoxHeadless -s omeka --vrde on &</code>
 
#* <code>VBoxHeadless -s omeka --vrde on &</code>
#* computers name in /etc/hosts and /etc/hostname to omeka
+
#* change computers name in /etc/hosts and /etc/hostname to omeka
 +
#* restarting Apache gives the error message: "apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 ..."
 +
#:: => solve this by adding ServerName nominatim as the last line in /etc/apache2/apache2.conf file
 
#* add additional users
 
#* add additional users

Revision as of 17:04, 2 December 2015

>> return to Cedeus IDE


Installing Omeka

Setup of Omeka VM

Setup of VM based on Ubuntu 1404 VM

  1. copying basicubuntu1404.vdi file and renaming to omeka.vdi
  2. creating the omeka VM on CedeusDB (ip.18):
    • VBoxManage createvm --name omeka --ostype Ubuntu_64 --register
    • VBoxManage modifyvm omeka --memory 8096
    • VBoxManage modifyvm omeka --cpus 4
    • VBoxManage modifyvm omeka --nic1 nat
    • VBoxManage storagectl omeka --name "SATA Controller" --add sata --controller IntelAhci
    • VBoxManage internalcommands sethduuid omeka.vdi
    • VBoxManage storageattach "omeka" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium omeka.vdi
    • VBoxManage storagectl omeka --name "IDE Controller" --add ide --controller PIIX4
    • VBoxManage modifyvm omeka --natpf1 "ssh,tcp,,20022,,22"
    • VBoxManage modifyvm omeka --natpf1 "apache,tcp,,20080,,80"
    • VBoxManage modifyvm omeka --vrdeport 7764
  3. start VM and change the computers name:
    • VBoxHeadless -s omeka --vrde on &
    • change computers name in /etc/hosts and /etc/hostname to omeka
    • restarting Apache gives the error message: "apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 ..."
    => solve this by adding ServerName nominatim as the last line in /etc/apache2/apache2.conf file
    • add additional users