Solved Installing Resourcespace

[kevinneal]

Hi I’m trying to install Resourcespace DAM on a DS216+ I’ve found instructions but the links are out of date and I’m trying to find ipkg but again all the links are down.

Does anyone have experience of installing RS recently who can help

 

[Rusty]

There are a number of Docker images for it out there... might be worth going that route. Not sure you will get a solution for it using the package center.

 

[kevinneal]

Thanks, I've looked at Docker, but I think I'm doing it wrong, I've downloaded every one of the resourcespace ones but cant get any to work

 

[Rusty]

errors?

 

[kevinneal]

Not errors as such, I just don't know what i'm doing ! The links to the docker images don't give much information, I don't know what I'm meant to put into the advanced settings to get it working

 

[Rusty]

Try and start with the one that has the most info on hub.docker.com. Take it from there and post back if you get stuck with it or have any questions on the matter.

We have a Docker dedicated forum so will move this topic there.

 

[kevinneal]

I've given a few of the Docker images a go, and to be honest I'm completely stumped, none of them give any real instruction, I get as far as launching the container then I'm lost !

 

[kevinneal]

this one for instance, does it make sense ? creecros/resourcespace-docker

 

[Rusty]

this one for instance, does it make sense ? creecros/resourcespace-docker

this might be more clear

Docker

You will need a running mysql 5.6 instance to make it work. If you haven’t used Docker before this might be a bit of bite for you but looking at the instructions in this compose, seems straightforward.

Post back if your get stuck

 

[kevinneal]

Thanks for taking a look, I guess my weekend will be learning about docker lol

 

[WST16]

my weekend will be learning about docker lol

I feel for you. I’m in the same position. I’ll be like Basil.

 

[kevinneal]

I'm stuck, I've tried doing it through the Docker app and I've tried doing it through ssh, just can't get it.

I've contacted the package maintainer and he isn't familiar with synology.

Would you Rusty, or anyone else be open to configuring it if I pay?

 

[Rusty]

I'll get around to see how it works in a few days when I get the time. No need for any $$. Glad to help out if and when I can.

 

[Shadow]

In general I also agree alot of Docker images come with total lack of documentation how to install/use them..

 

[Telos]

In general I also agree alot of Docker images come with total lack of documentation how to install/use them..

I had a prof, who when failing to correctly illustrate a proof, would stop and label the conclusion "IOCO" (in lieu of QED)... meaning "intuitively obvious to the casual observer", leaving his befuddled students to sort out the problem.

That's the sense I get with mots Docker images where there's no explanation of how to implement it... because it's IOCO

 

[one-eyed-king]

The image expects that volumes are used. The reason is quite clear: existing data in the target folder gets coppied into the volume, while a mount bind completly replaces the original folder. Since the UI only allows mount bind, volumes need to be used and the stack needs to be started from the ssh shell!

The original example did not care about the persistance of the mysql database data. I added the configuration parts to the config.

docker-compose.yml:

version: '2.2'
services:
  resourcespace-app:
    image: creecros/resourcespace-docker:latest
    restart: unless-stopped
    container_name: resourcespace
    ports:
      # change host port 8888 to whatever you need
      # host:container/protocol
      - 8888:80/tcp
    volumes:
      - include:/include
      - filestore:/filestore
  resourcespace-mysql:
    image: mysql:5.6
    restart: unless-stopped
    container_name: resourcespace-mysql
    environment:
      MYSQL_DATABASE: resourcespace
      MYSQL_ROOT_PASSWORD: Un1c0rn
    volumes:
      - database:/var/lib/mysql
volumes:
  filestore:
    driver: local
    driver_opts:
      type: none
      # change path in device to an existing path on your diskstation!
      device: /volume1/docker/resourcespace/filestore
      o: bind
  include:
    driver: local
    driver_opts:
      type: none
      # change path in device to an existing path on your diskstation!
      device: /volume1/docker/resourcespace/include
      o: bind
  database:
    driver: local
    driver_opts:
      type: none
      # change path in device to an existing path on your diskstation!
      device: /volume1/docker/resourcespace/database
      o: bind

Make sure to store the content of aboves block in a file called docker-compose.yml on your ds (e.g. in /volume1/docker/resourcespace) . Make sure that the folders used in device exist before a docker-compose up -d is called, otherwise the command will raise an error.

In case you don't want to use port 8888 on your DS, replace the port to a free port of your choosing. If you want to store the data in a different location, make sure to change the values of the device lines.

Good luck!

 

[one-eyed-king]

I had a prof, who when failing to correctly illustrate a proof, would stop and label the conclusion "IOCO" (in lieu of QED)... meaning "intuitively obvious to the casual observer", leaving his befuddled students to sort out the problem.

That's the sense I get with mots Docker images where there's no explanation of how to implement it... because it's IOCO

People should stay away from images that don't discribe how they are ment to be used and what (and why!) preconditions need to be fullfilled.

Usualy they are work in progress images that suite the need of the creator and are rarely ment to be used by others.
Though, creecros/resourcespace-docker provides enough information to get started. If the author would have mentioned that the image relies on the copy back mechanism for volumes, it would have saved me 10 minutes :/.

Also the whole image is pretty primitive: no env variables that allow to configure the app and no entry point script that could use them to configure the application. This image was created with minimum effort.

 

[kevinneal]

I'll get around to see how it works in a few days when I get the time. No need for any $$. Glad to help out if and when I can.

Thanks that would be great if you are able to

 

[kevinneal]

Make sure to store the content of aboves block in a file called docker-compose.yml on your ds (e.g. in /volume1/docker/resourcespace) . Make sure that the folders used in device exist before a docker-compose up -d is called, otherwise the command will raise an error.

In case you don't want to use port 8888 on your DS, replace the port to a free port of your choosing. If you want to store the data in a different location, make sure to change the values of the device lines.

Good luck!

Thanks for this, I've made the yml file and when I run the docker-compose command it says:
Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

 

[one-eyed-king]

you need to be root to run docker cmds. just type "sudo -i" (with the quotes of course) on the shell to elevate to root.

update: should have been without the quotes cough