njfranck

No, I do not really need 10 instances on the same server. I was just trying to understand the different options ;-) This is the situation on my server [root@pamuk0 DEVELOPMENT njfranck]# ps aux | grep spawn root 29409 0.0 0.0 112708 976 pts/0 S+ 15:38 0:00 grep --color=auto spawn [root@pamuk0 DEVELOPMENT njfranck]# ps aux | grep iipsrv root 29416 0.0 0.0 112708 976 pts/0 S+ 15:38 0:00 grep --color=auto iipsrv iip 31866 0.0 0.1 35916 4584 ? Ss 03:19 0:00 /usr/lib64/cgi-bin/iipsrv.fcgi iip 31867 0.0...

What is the best way to setup a list of iipsrv instances? What I've done so far, on a centos 7 server: create a systemd file, that starts the iipsrv.fcgi with spawn-fcgi: [Unit] Description=iipsrv After=network.target [Service] Type=forking EnvironmentFile=/etc/sysconfig/iipsrv.conf ExecStart=/bin/spawn-fcgi -f /usr/lib/cgi-bin/iipsrv.fcgi -U iip -u iip -a 127.0.0.1 -p 9000 -P /var/run/iipsrv.pid PIDFile=/var/run/iipsrv.pid Restart=always [Install] WantedBy=multi-user.target create multiple servers,...

Yes, and they proximately give the same answer: put a gateway in front of your iipsrv (in my case openresty to make it fast). iipsrv is kept simple by design, because everyone has his/her own use cases for lookup, authorization..

A few hints: you should not provide access to the proxied url /iipsrv.fcgi. Anyone can construct a random url. By the way: iiif does not allow, or like urls with query parameters. It likes path-only urls, because that gives the impression that these are static images (because level-0 is also iiif compliant). In nginx you can do the following: make /iipsrv.fgi an internal path. Paths like this are only accessable for internal rewrites, internal requests and x-accel-redirect. configure path /images/:id/info.json,...

Try the universalviewer or mirador? The iipsrv supports the iiif image api (and is one of the fastest implementations). cf. http://projectmirador.org/demo/advanced_features.html cf. http://universalviewer.io/examples/ cf. https://github.com/UniversalViewer/universalviewer cf. https://github.com/ProjectMirador/mirador

Maybe try out a newer version of the iipsrv? The official package for 1.0 is out (for Centos 6/7, Ubuntu) for quite some time. Version 0.9 is old I'm afraid.

So, install the iipserver on the server where the images are. You can still host the viewer on your own site, and point it to endpoint on that other server. As I said: make sure that image-server adds cross-origin-headers to its responses.

You can always turn the things the other way around: host the iipserver on the same server where the images are. make sure the proxy server (nginx, apache) add cross-origin-headers to the responses of iipsrv: Access-Control-Allow-Origin: * Access-Control-Allow-Headers: accept, origin, x-requested-with, content-type, x-transmission-session-id, authorization, cookie Access-Control-Expose-Headers: X-Transmission-Session-Id Access-Control-Allow-Methods: GET, POST, OPTIONS, X-Transmission-Session-Id Access-Control-Allow-Credentials:...