All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
dspace-7.2
) or branch.[dspace-angular].
Install any updated local dependencies using Yarn in the [dspace-angular]
source code directory:
Code Block |
---|
# change directory to our repo cd [dspace-angular] # install/update the local dependencies yarn install |
Build the latest User Interface code for Production: This rebuilds the latest code into the [dspace-angular]/dist
directory
Code Block |
---|
yarn build:prod |
[dspace-angular]/dist
) to a different directory (which we refer to as [dspace-ui-deploy]
) in order to keep your running UI separate from the source code. While it's still possible to run the UI using "yarn start" or "yarn run serve:ssr" (both of which use [dspace-angular]/dist
),
that older approach will mean that your site goes down / becomes unavailable anytime you rebuild (yarn build:prod). To solve this issue:[dspace-ui-deploy]
location as described in the Installation documentation.[dspace-angular]/dist
folder to that location, as described in the Installation documentation.If upgrading from 7.0 or 7.1, migrate your UI Configurations to YAML. In 7.2, the format of the UI configuration file changed from Typescript to YAML to support runtime configuration. This means that the older ./src/environment/environment.*.ts
configuration files have all been replaced by corresponding ./config/config.*.yml
configuration files (e.g. environment.prod.ts → config.prod.yml).
In 7.3, a new "eager-theme.module.ts" and "lazy-theme.module.ts" has been added to both the "custom" and "dspace" themes to improve performance. Make sure to copy those to your custom theme. Additionally, this new "eager-theme.module.ts" for your theme MUST be imported/enabled in "src/themes/eager-themes.module.ts". For example, for a local theme under "src/theme/my-theme":
Code Block | ||
---|---|---|
| ||
import { EagerThemeModule as MyThemeEagerThemeModule } from './my-theme/eager-theme.module';
...
@NgModule({
imports: [
MyThemeEagerThemeModule,
],
}) |
Using a tool like "git diff" from the commandline is often an easy way to see changes that occurred only in that directory.
Code Block |
---|
# Example which will show all the changes to "src/themes/dspace" (and all subfolders)
# between dspace-7.1 (tag) and dspace-7.2 (tag)
git diff dspace-7.1 dspace-7.2 -- src/themes/dspace/ |
const DECLARATIONS
" section), and also registers new Modules, i.e. new UI features, (in the "@NgModule
" → "imports" section). Make sure those sections are updated in your copy of this file!const DECLARATIONS
" section), and also registers new Modules, i.e. new UI features, (in the "@NgModule
" → "imports" section). Make sure those sections are updated in your copy of this file!If you are using PM2 as described in the Installing DSpace instructions, you'd stop it and then start it back up as follows
Code Block |
---|
# Stop the running UI pm2 stop dspace-ui.json # If you had to update your PM2 configs, you may need to delete your old configuration from PM2 # pm2 delete dspace-ui.json # Start it back up pm2 start dspace-ui.json |
If you are using a different approach, you simply need to stop the running UI, and re-run:
Code Block |
---|
# First stop the running UI process by killing it (or similar) # You MUST restart the UI from within the deployment directory # See Installation Instructions for more info on this directory cd [dspace-ui-deploy] # Then restart the UI via Node.js node ./dist/server/main.js |
...