How to run a quick test installation of FSI Server
docker run --rm -it -p 8080:8080 -t neptunelabs/fsi-server
This command is solely for quickly testing your FSI Server docker image, which you can afterwards access via http://localhost:8080/fsi/interface/
--rm will remove the container after run.
-i will issue a pseudo-tty and keep STDIN open even if not attached. This allows you to use the container like a traditional VM as long as the bash prompt is running.
-p 8080:8080 exposes the container to port 8080.
Please note that this is just for testing purposes and not persistent. For a persistent installation, please see below.
Create Persistent Data Directory on your host
Since FSI Server is usually used to manage a large amount of images, we recommend creating a persistent directory for storing the images on your host.
This also has the advantage that it is easier to change the container for an update while preserving the image storage.
mkdir -p /opt/fsi-data
mkdir creates the directory, the
-p flag is used to create parent directories if needed.
Create Persistent Data Structure in /opt/fsi-data
docker run --rm -t -i -v /opt/fsi-data:/srv/fsi/mounts neptunelabs/fsi-server fsi create_persistent
This creates the persistent data structure in
Create FSI Server Container and start it
docker run --name fsi-server -p 8080:8080 -v /opt/fsi-data:/srv/fsi/mounts -t neptunelabs/fsi-server
fsi-server is the name assigned to the container,
-p 8080:8080 exposes it to port 8080,
-v defines that there will be a volume mounted at /opt/fsi-date so you have persistent access to config files, storage/connectors etc. even if the container is removed.
Run FSI Server benchmark
docker exec -it fsi-server bin/fsi benchmark
Please keep in mind that for a full benchmark (including the Storage benchmark) a minimum storage of 50GB need to be available.
It is also possible to benchmark only certain parts of FSI Server, for example:
docker exec -it fsi-server bin/fsi benchmark encoder
List of available commands for benchmark:
Use FSI Server in prodcution mode
You can download the software and try it as long as you like. There are no feature limitations or performance restrictions in the unregistered version, besides watermarks being displayed. We also provide a free 60 day key for testing purposes without watermarks, you can see how the get one here.
After the trial period expired you can add a full licence key.
Our solution is flexible and can be tailored to your needs and business – whether you are a small, medium or large enterprise, if you have a small or a big amount of page impressions monthly – our editions cover all of those cases. You can choose to install the software on your own hardware or use dedicated servers or shared hosting services provided by us – we offer a tailored setup matching your requirements. You can learn more about the available options here.
Assign RAM to FSI Server while creating the container
docker run --name fsi-server -d -e "XMX=4g" -p 8080:8080 -v /opt/fsi-data:/srv/fsi/mounts -t neptunelabs/fsi-server
-e "XMX=4g" assigns 4GB RAM to FSI Server.
Connect to FSI Server from an application in another docker container (e.g. Solr)
Please note that the following steps need to be done BEFORE the FSI Server container is created.
docker pull solr:alpine
We recommend using the alpine version of Solr since this version uses less space than the normal version.
Create Solr core
docker run --rm -t -i -v /opt/fsi-data:/srv/fsi/mounts neptunelabs/fsi-server fsi create_solr_core
Start a Solr Server Container with FSI Server Core
docker run --name fsi-solr -d -p 8983:8983 -v /opt/fsi-data/solr-core/fsi-server:/opt/solr/server/solr/fsi-server -t solr:alpine
Create FSI Server container, link it with Solr and start it
docker run --name fsi-server -p 8080:8080 -v /opt/fsi-data:/srv/fsi/mounts --link fsi-solr:solr -t neptunelabs/fsi-server
Available fsi commands
Configuring FSI Server, creating connectors, etc.
For in-depth information on how to configure FSI Server, please visit the FSI Server online manual.