Hi Petros, Apologies for the delay in answering your question... After seeing your question, we realized that our Installation Documentation was recommending a setup which results in​ this issue you are experiencing.
Simply put, if you run your UI from the build location ([dspace-angular]/dist), then anytime you rebuild, then the running UI will be unavailable during the rebuild process. This is what you are noticing. However, if you move the built UI to a different location & run it from there, then you are able to rebuild the UI at any time without impacting the running UI. This minimizes downtime in Production scenarios. Unfortunately, though, the build process of 7.0 & 7.1 made this setup much harder to achieve. So, we recommend you first upgrade to 7.2. Our 7.2 Installation Docs have been updated now to recommend running your UI from a different "deployment" directory. See https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation If you have further questions, let us know on this list. Tim ________________________________ From: 'Petros Grammatikopoulos' via DSpace Technical Support <[email protected]> Sent: Thursday, April 7, 2022 5:30 AM To: DSpace Technical Support <[email protected]> Subject: [dspace-tech] Angular builds question - Changes in static DSpace content Greetings As I am not entirely familiar with Angular as a framework, and most particularly the build process of the production environment of the DSpace 7 Angular frontend, I have an inquiry for DSpace 7.0: When I make a change in a static content file, let's say the end-user-agreement page for example, do I have to redo the whole production build for the change to be applied to the frontend (yarn run build:prod) or is there a faster way? The limited resources I currently have in setting up this project (time, people) do not allow me to look through setting up some sort of developer environment, as I briefly saw it mentioned in the wiki. I am setting this up as a side-project. I would like to know if there's a faster way for straight-to-production changes like the one mentioned above, but without messing about too much -if at all- with the default configs and buildfiles. Currently a whole frontend build takes 10 minutes and is perceived as downtime by endusers, so that's what I'm trying to avoid for mere static page content changes... Thank you in advance and I really appreciate your time if you have a "shortcut" for this procedure in mind. Email Disclaimer The content in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately and delete this e-mail and any attachments from any computer storage or other medium. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free. Any views or opinions presented are solely those of the author and do not necessarily represent those of this organisation. -- 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/3b489609-36b5-4771-85b5-9d9742efb0b0n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/3b489609-36b5-4771-85b5-9d9742efb0b0n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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/PH0PR22MB3274762F5C671D53045CE522EDEC9%40PH0PR22MB3274.namprd22.prod.outlook.com.
