access dspace frontend without 4000 port

[sunit...@gmail.com]

Is it possible to run dspace 7 server frontend without 4000 port on a production server.

It would be more easy to access  dspace frontend without any port or using /dspace before URL such as  https://dspaceserver/dspace or just https://dspaceserver than adding 4000 port.

If possible pl. share steps to configure.

reg

Sunita Barve

[Tim Donohue]

Hi,

See our Installation Documentation, step 9, for one example of running the User Interface on HTTPS (port 443): https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-InstallingtheFrontend(UserInterface)

If you have more specific questions, feel free to ask on this list.

Tim

[Armin Wenz]

Hi,

we are running DSpace 6.3/JSPUI with fulltext search enabled. `dspace
filter-media` is running nightly and searching within DSpace works fine.

Now we want to restrict the fulltext search to a filter in the advanced
search and keep the fulltext out of the simple search results.

Is this even possible? And if yes, can anybody point me to a
documentation. I haven't found anything in Discovery DSpace Docu (maybe
I'm to blind to see)

thanks for any answer
--

Armin Wenz
Universitätsbibliothek Mainz
Leitung Bibliotheksanwendungen
Jakob-Welder-Weg 12
55128 Mainz
Tel.: +49 6131 39-29830
http://www.ub.uni-mainz.de

[sunit...@gmail.com]

Dear Tim

Thank you for responding immediately.

We  are using our server for many services.  The main http(s): hostname.domanname is used for our library home page. 

The library does not have one more hostname.  I am using Ubuntu 20.04.3. Using the proxy statements as the following lines:

ProxyPass /dspace http://localhost:4000/

ProxyPassReverse /dspace http://localhost:4000/

results in garbled display without graphics. I enabled apache proxy related modules

Please let me know how do I achieve, my dspace url as

http(s)://hostname.domainname/dspace or

http://localhost/dspace

reg

[Tim Donohue]

To run the UI off a subpath, you'd likely need to modify your UI's "nameSpace" setting to specify that path:

https://github.com/DSpace/dspace-angular/blob/dspace-7.1/src/environments/environment.common.ts#L15

So, this should likely be
nameSpace: '/dspace', 

You also will need to modify the '<base href="/">' tag in both the "index.html" and "index.csr.html" to have that same path: '<base href="/dspace/">'.  Those lines that you need to modify are at: 

https://github.com/DSpace/dspace-angular/blob/dspace-7.1/src/index.html#L6

and

https://github.com/DSpace/dspace-angular/blob/dspace-7.1/src/index.csr.html#L6

Then, you may be able to get your ProxyPass settings to work like this...

ProxyPass /dspace http://localhost:4000/dspace/

ProxyPassReverse /dspace http://localhost:4000/dspace/

Unfortunately, though, I've found that this setup doesn't fully work as expected (it's a bug in 7.1 which should be fixed in 7.2 due on Feb 7). While the above setup will get your UI to respond on http://localhost:4000/dspace/, some of the styles appear to not be loaded properly.  I've just created a PR to fix this in 7.2 which you might be able to use to guide you in getting this to work correctly in 7.1.  See https://github.com/DSpace/dspace-angular/pull/1488   Or, you could wait for the 7.2 release, which is due out on Feb 7.

Your other alternative would be to create a new subdomain (e.g. dspace.your.url), which would work perfectly OK with the UI running at http://localhost:4000/

If you have more questions, let us know on this list

Tim