Hello,
Would it be possible to install omeka classic or ~multiple omeka classics~ on different subdirectories?
IE
ournicewebsite.edu/omeka1
ournicewebsite.edu/omeka2
ournicewebsite.edu/collectionbuilder
I have been trying to do this with apache but cannot get it to work with the redirects.
Thank you,
Jonathan
I was able to figure it out
by updating the .htaccess file rewrite settings
RewriteBase /omeka1
AND
having the Alias in the virtualhost file
<VirtualHost *:80>
ServerName ournicewebsite.edu
DocumentRoot /var/www/omeka1
<Directory "/var/www/omeka1" >
Options FollowSymLinks
AllowOverride All
Require all granted
</Directory>
Alias /omeka1 "/var/www/omeka1"
</VirtualHost>
thank you for reading. have a nice day.
Sorry, I actually have another update. This is not working as I thought it should.
The /omeka1 site is showing up on /
in addition to /omeka1
How can I prevent this from happening or so that my omeka classic site is ONLY appearing at the subdirectory?
Hi @kiritharan ,
I can’t provide an answer to this problem, but I’m wondering if you can use subdomains instead of subdirectories.
I’ve never tried to put Omeka in a subdirectory and I would say in my experience, it’s far more common to see
omeka1.ournicewebsite.edu
omeka2.ournicewebsite.edu
Each site could be in a different directory on the server, but you would configure the subdomains to point to the corresponding directory.
Typically Omeka works just fine in a subdirectory with no setting of RewriteBase or adding Alias or special VirtualHosts, etc.
It’s quite common for people to have Omeka installed at a location other than the server root.
thank you @fackrellj . i can do a subdomain if push comes to shove but this would not work aesthetically with our other domains.
@jflatnes do you have any examples, or documentation, or people I can reach out to who may have some experience in doing this, or suggestions regarding my configuration that i have shared above?
I’ll just add that I install Omeka Classic and Omeka S in subdirectories regularly with no additional configuration changes. However, if that root directory is the home of something like WP that has it’s own rewrite rules, it won’t work.
The typical situation for hosting an Omeka site, whether in a subdirectory or not, just uses a “normal” vhost, along these lines:
<VirtualHost *:80>
ServerName ournicewebsite.edu
DocumentRoot /var/www/html
<Directory "/var/www/html">
Options FollowSymLinks
AllowOverride All
Require all granted
</Directory>
</VirtualHost>
Inside /var/www/html
if you have separate folders omeka1, omeka2, collectionbuilder, that should “just work”, and they’d be available at ournicewebsite.edu/omeka1, etc.
Using /var/www as the DocumentRoot directly is also fine, as you had it; I only changed my example to /var/www/html as that’s the more common default DocumentRoot. What matters is: the usual setup would be, just make the parent folder that contains all the subdirectory installs the DocumentRoot, then don’t have any Alias or similar configurations.
thank you everyone this helped~
everything is working. i had tried putting everything in /var/www/X instead of /var/www/html/X