Difference between revisions of "How to build a development environment from source control"

From EPrints Documentation
Jump to: navigation, search
(Ubuntu 14.04)
(Ubuntu 14.04)
Line 39: Line 39:
 
cd eprints
 
cd eprints
 
bin/generate_apacheconf
 
bin/generate_apacheconf
 
+
sudo service apache2 restart
 
+
  
 
</pre>
 
</pre>

Revision as of 13:22, 18 November 2015

This article explains the various ways you can build a development environment for EPrints source contributions. If you have a method not listed here then please add it. Instructions assume familiarity with EPrints and the command line. You can use repositories built in this way to test contributions to EPrints source before pushing them to the git remote.

If you find bugs with any of these instructions please update them

Ubuntu 14.04

Take a clean ubuntu 14.04 build

sudo su
apt-get install git
echo "deb http://deb.eprints.org/ nightly/
deb-src http://deb.eprints.org/ source/" > /etc/apt/sources.list.d/eprints.nightly.list
apt-get update
apt-get build-dep eprints
ln -s /home/<yourusername>/eprints /usr/share/eprints3
echo "Include /usr/share/eprints3/cfg/apache.conf" > /etc/apache2/sites-available/eprints-git.conf
sudo a2ensite eprints-git

su <yourusername>
cd ~
git clone git@github.com:eprints/eprints.git


echo "package EPrints::SystemSettings;

\$EPrints::SystemSettings::conf =
{
        'base_path' => '/usr/share/eprints3',
        'version_id' => 'git',
        'version' => 'EPrints (development version)',
        'user' => '$USER',
        'group' => '$USER',
        'smtp_server' => 'smtp',
};

1;"

cd eprints
bin/generate_apacheconf
sudo service apache2 restart

CentOs

User-space EPrints (when EPrints is already installed on the VM)

See: https://github.com/eprints/apache_rhel


Debian

User-space

See: https://github.com/eprints/apache_debian