Describe installation procedure for applications on Tarantool

[opomuc]

Please provide a complete manual where to place custom Lua modules and other configurations files (eg. for tarantoolctl tool) and how to deploy an application written on Tarantool.

There was no common opinion on this in Tarantool chat. Should it be /usr/share/tarantool or /usr/local/tarantool for example.

[Totktonada]

I think /usr PREFIX is exclusively for files under a package manager control, but /usr/local PREFIX (as well as /opt) is for 'manually' installed packages. Modules should follow tarantool install location (at least they do it), so a module install directory depends on how tarantool installed. Correct me if I’m wrong in some way.

There are ways to determine PREFIX with which tarantool was installed. The first one is to use FindTarantool.cmake (see avro-schema for example). By the way, we are going to include this file to tarantool-{dev,devel} packages in the future releases ( tarantool/tarantool#3147 ). The second way is to parse tarantool --version output (see stat module for example). It does not require headers (and so dev/devel packages) being installed.

It is possible to separate tarantool install directory from a module install directory, e. g. add some custom package.{path,cpath} or use rocks (which look for .rocks directory recursively up to a filesystem root).

And I just observed: I have tarantool installed into /usr, but package.{path,cpath} have paths with both prefixes. I guess one can always install modules into /usr/local/share/tarantool and /usr/local/lib64/tarantool (Lua and C) and everything will work everywhere. But I suggest to leave /usr (or a PREFIX a package manager provides) for installing from packages.

[kyukhin]

IMHO, Sasha clearly described how it should work. @lenkis what feedback do you expect?