All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
dspace-7.0-beta3
) or branch.Install all necessary local dependencies by running the following from within the unzipped "dspace-angular" directory
Code Block |
---|
# change directory to our repo cd dspace-angular # install the local dependencies yarn install |
Modify the "rest" section of the [dspace-angular]/src/environment/environment.common.ts
configuration file, pointing it at your installed DSpace Backend. For example:
Code Block |
---|
// This example is valid if your Backend is running at http://localhost:8080/server/
// It should be kept in sync with the value of "dspace.server.url" in the backend local.cfg
rest: {
ssl: false,
host: 'localhost',
port: 8080,
// NOTE: Space is capitalized because 'namespace' is a reserved string in TypeScript
nameSpace: '/server/api'
} |
[dspace-angular]/src/environment/environment.common.ts
configuration file to match the host & port that you plan to run the UI from. By default, these settings assume you will run the UI from http://localhost:4000/Code Block |
---|
// This example is valid if your UI will be running at http://localhost:4000 // It should be kept in sync with the value of "dspace.ui.url" in the backend local.cfg ui: { ssl: false, host: 'localhost', port: 4000, // NOTE: Space is capitalized because 'namespace' is a reserved string in TypeScript nameSpace: '/' } |
Start the application
Code Block |
---|
# build and start the application yarn start |
...
src/environments/environment.common.ts
EXACTLY MATCH the Backend's local.cfg
dspace.ui.url
MUST reference the same URL as the Frontend's "ui" configuration section. Modes (http vs https), ports, hostnames AND nameSpace (or path) must all match.dspace.ui.url
configuration, as they are the default ports for HTTP and HTTPS respectively.dspace.server.url
MUST reference the same URL as the Frontend's "rest" configuration section. Modes (http vs https), ports and hostnames must all match.dspace.server.url
configuration, as they are the default ports for HTTP and HTTPS respectively.Also keep in mind that the "dspace.server.url" configuration should NOT include the "/api" path, whereas the "rest" configuration section MUST include that path (as "/api" is the location of the REST API within the server webapp).rest.cors.allowed-origins
specifies the client URLs which are allowed login access to the Backend. It MUST include the Frontend URL (though by default it does) or else the backend will block all access to the frontend.