WARNING - My method of using the relative paths to the earlier DS 7.1 directory did run under the yarn env:yaml script, but it did not produce a useful config.prod.yml file. Angular insisted on listening at localhost:8080, rather than localhost:4000. I don't know why this didn't work, but Mohammad's suggestion of editing the config.example.yml to define my URLs and ports worked much better and easier.
On Wednesday, February 9, 2022 at 2:15:00 AM UTC-5 [email protected] wrote: > On Wednesday, February 9, 2022 at 2:47:08 AM UTC+3 Chris Clawson wrote: > >> Everything seemed to finish well, although a full system reboot failed >> to start angular as a service. I guess this is my last barrier to a >> functional upgrade, but it is the stuff of a new thread if I need help. >> > > You need to replace the ExecStart line in the service startup script as > you see below and you also need to change the WorkingDirectory path to > reflect the new path if it's changed. > vi /lib/systemd/system/dspace-angular.service > ExecStart=/usr/bin/node dist/server/main > WorkingDirectory=/opt/dspace-angular > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/90d07c77-22cb-4df5-8f5a-a25756a19d34n%40googlegroups.com.
