Skip to content

How to ship your application with tarantool #667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Tracked by #2572
knazarov opened this issue Nov 26, 2018 · 2 comments
Open
Tracked by #2572

How to ship your application with tarantool #667

knazarov opened this issue Nov 26, 2018 · 2 comments
Labels
guidelines raw idea [special status] Not ready for size estimation

Comments

@knazarov
Copy link

There should be a chapter that describes how to ship tarantool applications in production:

  • installing dependencies (rocks)
  • packing
  • deploying
@Totktonada
Copy link
Member

Personally I think delivering as RPM / Deb is good and rocks are good for development and / or unusual cases (say, non-root installation). We can deprecate standard package managers for our teams (except ones where we have agreement with an operation team that we'll deliver rpms), but it will not change minds in the outside world. Many (I think) persons want to deliver its applications as rpms.

@knazarov
Copy link
Author

Delivering applications as rpms/docker images/debs/tar.gz is orthogonal to installing rocks dependencies, which should (in my opinion) be done with tarantoolctl rocks install under the .rocks directory in app root

@lenkis lenkis added the raw idea [special status] Not ready for size estimation label Dec 19, 2018
@p7nov p7nov added dev_guide and removed dev_guide labels Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidelines raw idea [special status] Not ready for size estimation
Projects
None yet
Development

No branches or pull requests

5 participants