-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #302 from virtual-imaging-platform/develop
- Loading branch information
Showing
88 changed files
with
1,473 additions
and
1,777 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,8 +24,55 @@ You may name your branch anything except master, develop, release-*, or hotfix-* | |
* Push your commits to Github (your fork). | ||
* Make a pull request to merge feature branch (in your fork) to development branch (in the base repository). | ||
|
||
# Installation instructions | ||
# Production installation instructions | ||
|
||
You can follow the instruction [here](https://github.com/virtual-imaging-platform/Complementary-tools/blob/develop/README.md) | ||
|
||
You can contact us at [[email protected]]([email protected]) for precisions. | ||
|
||
# Local test installation instructions | ||
|
||
It is possible to launch a local vip instance in a tomcat on a linux machine. | ||
This is only useful for testing purposes as most of the features are simulated and many are still to be implemented and do not work yet. | ||
Here are the instructions to configure a local vip instance : | ||
- create a empty folder that will contain all the configuration files and simulated data. `/path/to/vip/local/folder` will be its path used in the next instructions | ||
- unzip the `local-config.zip` archive available in `vip-local/src/main/resources` in `/path/to/vip/local/folder`. This should contain 3 `.conf` files | ||
- create a `$HOME/.vip` directory and a `$HOME/.vip/local-config-folder.properties` file | ||
- put `vipConfigFolder = /path/to/vip/local/folder` in the `$HOME/.vip/local-config-folder.properties` file | ||
|
||
Then, install vip in your local tomcat : | ||
|
||
1. Build the vip-local war with `mvn clean package` at the root of the `VIP-portal` project. | ||
2. Put the `vip-portal/target/vip-portal-[...]-local.war` file in the `$TOMCAT_HOME/webapps` directory | ||
3. Add the folowing lines in `$TOMCAT_HOME/conf/context.xml` (database jndi configuration), and edit `path/to/vip/local/folder/vip` to the real path in `url` | ||
``` | ||
<Resource name="jdbc/vip" auth="Container" type="javax.sql.DataSource" | ||
username="sa" | ||
password="" | ||
driverClassName="org.h2.Driver" | ||
description="VIP local h2 Connection" | ||
url="jdbc:h2:/path/to/vip/local/folder/vip" | ||
maxActive="100" | ||
maxIdle="50" /> | ||
``` | ||
4. Create or adapt the `$TOMCAT_HOME/bin/setenv.sh` file with these lines (edit `path/to/vip/local/folder/vip` to the real path) : | ||
|
||
``` | ||
export CATALINA_OPTS="$CATALINA_OPTS -Dspring.profiles.active=local,config-file,jndi-db" | ||
export CATALINA_OPTS="$CATALINA_OPTS -DvipConfigFolder=/path/to/vip/local/folder" | ||
``` | ||
|
||
5. That's it, start tomcat (`bin/startup.sh`). Access vip on `localhost:8080/vip-portal-[...]-local` (adapt with the war name and your tomcat host/port configuration) | ||
|
||
### Local instance notes | ||
|
||
- The default admin email/password is `[email protected]`/`localAdminPassword`. | ||
- all is not working perfectly yet, expect to see some error messages. The home page, files transfers and execution launchs shoud work, but application imports and the page with execution details are not implemented at the moment. | ||
- vip do not send email but logs them | ||
- at the moment, logging is done in the `$HOME/.vip/vip.log` file | ||
|
||
|
||
|
||
|
||
|
||
|
||
To be done. Until this section is written, install at your own risks or | ||
contact us at | ||
[[email protected]]([email protected]). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.