Commit 3aa778c4 authored by Gerrit Hübbers's avatar Gerrit Hübbers 🃏
Browse files

Remove redundancy from documentation

parent 08d51918
......@@ -59,7 +59,6 @@ mysql --user=root --password --host=localhost --port=3306 --protocol=TCP --verbo
#### Linux user and filesystem setup
Create a `dda` Linux user:
```
adduser --system --no-create-home --disabled-login --group dda
......@@ -76,7 +75,6 @@ mvn clean package -Pprod -DskipTests
This will create the executable web application artifact located at `target/dda-wizard.war`.
Next, create a directory where the DDA binary will reside:
```
sudo sh -c "mkdir /srv/dda"
```
......@@ -96,7 +94,6 @@ Update file `/srv/dda/application-prod.yml` to reflect your production environme
* `ingester.targetCollection`: the DSpace collection *ID* (not collection *handle*) of DDA's import collection which you created in step [*Creating a Document Deposit Assistant DSpace collection*](#creating-a-document-deposit-assistant-dspace-collection).
Set correct directory and file permissions:
```
sudo sh -c "chown -R dda:dda /srv/dda/ && chmod -R u=rx,g=,o= /srv/dda"
# This will set ownership of directory /srv/dda and all its content to user and group `dda`
......@@ -105,13 +102,11 @@ sudo sh -c "chown -R dda:dda /srv/dda/ && chmod -R u=rx,g=,o= /srv/dda"
#### Service registration
Assuming you want to install DDA as a *SystemV init.d* service, first create a symlink from `/etc/init.d/dda-wizard` to the executable WAR file:
```
sudo ln -s /srv/dda/dda-wizard.war /etc/init.d/dda-wizard
```
Second, register DDA to start up and shut down during appropriate Linux lifecycle phases:
```
sudo update-rc.d dda-wizard defaults
......@@ -120,7 +115,6 @@ sudo update-rc.d dda-wizard defaults
```
Now start up DDA:
```
sudo service dda-wizard start
......@@ -179,7 +173,6 @@ Install the following software development tools:
Set environment variables according to http://stackoverflow.com/a/26640589 and put Maven's `bin` directory on your computer`s `${PATH}`.
Start Cygwin and git-clone the dda-wizard project:
```
cd ~/git/
......@@ -188,7 +181,7 @@ git clone git@git.gesis.org:dda/dda-wizard.git
Start Eclipse. Select *File* -> *Import...* -> *Maven* -> *Existing Maven Projects* -> *Browse* to `~/git/dda-wizard` -> Click *OK* -> Click *Finish*. Wait for Eclipse to finish importing the project - in case Eclipse asks for installing additional *Maven plugin connectors*, agree to it.
Install npm dependencies once
Install npm dependencies once:
```
cd ~/git/dda-wizard/
npm install
......@@ -201,35 +194,10 @@ cd ~/git/dda-wizard/
mvn
```
## Technical overview
This application was generated using [JHipster 2.27.1](https://jhipster.github.io/v2-documentation/).
Before you can build this project, you must go through the following steps once.
DDA uses [Node.js](https://nodejs.org/) to build the project and run a development web server. Depending on your system, you can install Node.js either from source or as a pre-packaged bundle.
DDA was generated with jHipster 2.27.1. If you want to extend the DDA source code base with additional jHipster entities, you will need exactly that version:
npm install -g yo
npm install -g generator-jhipster@2.27.1
[Grunt](http://gruntjs.com/) is DDA's front-end build system. Install the grunt command-line tool globally with:
npm install -g grunt-cli bower
After installing Node, run the following command to install front-end development tools such as [Bower](http://bower.io/) and [BrowserSync](http://www.browsersync.io/). You will only need to run this command whenever front-end dependencies change in file `package.json`:
npm install
Run the following commands in two separate terminals to create a blissful development experience where your browser auto-refreshes whenever DDA project files change in your filesystem.
mvn
grunt
Bower is used to manage CSS and JavaScript dependencies. You can upgrade dependencies by specifying a newer version in file `bower.json`. You can also run `bower update` and `bower install` to manage dependencies.
Add the `-h` flag on any command to see how you can use it. For example, `bower update -h`.
## Staging
### Initial setup
The staging environment shall be as close as possible to the production environment. Therefore, run the same commands as listed in the [Database setup][#database-setup] chapter.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment