It is a bad practice to expose your solr instance to the public, your data could be manipulated or worse, deleted. Apart from blocking solr’s port 8983 using the firewall, it is also good practice to run solr on localhost only if the service that consumes solr services is running on the same host, eg dspace. This guide is a record of how you can run solr 8.x on localhost:8983
Read MoreDSpace 7 UI Customization: Enable New Custom Theme
Prerequisites
Step 1: Copy custom theme and rename to a different name
Step 2: Register the new theme as shown below in angular.json
Read MoreDSpace 6.x Backup Guide with an Automation Script
Making backups of your DSpace is an essential task to ensure that you can recover from any disaster that might occur, such as hardware failure or data corruption. This guide assumes a dspace 6.x or older setup. Here are the steps you can follow to perform a backup of the repository.
Read MoreDSpace mail.extraproperties working settings for gmail smtp
mail.extraproperties = mail.smtp.socketFactory.port=465, \
mail.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory, \
mail.smtp.socketFactory.fallback=false, \
mail.smtp.starttls.enable=true, \
mail.smtp.auth=true, \
mail.smtp.ssl.protocols=TLSv1.2, \
mail.smtp.ssl.trust=smtp.gmail.com
DSpace 6: Configure apache2 as reverse proxy in front of tomcat
This post guides you on how to configure apache2 to run as a reverse proxy in front of tomcat. The reason I personally use apache2 instead of directly exposing tomcat is because it becomes easy to install SSL certicates and automate their renewal. This is also best practice as it is not recommended to expose your tomcat servlet to the world.
This guide assumes that you have installed DSpace 6, or any other application that you wish to run behind a proxy. It also assumes that it is configured to run on port 8080 which is the default port number for a tomcat installation.
Read More