Source: ruby-foreman
Section: ruby
Priority: optional
Maintainer: Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Uploaders: Per Andersson <avtobiff@gmail.com>,
Build-Depends: debhelper-compat (= 12),
               gem2deb,
               rake,
               ruby-bundler,
               ruby-dotenv,
               ruby-fakefs,
               ruby-rr,
               ruby-rspec,
               ruby-simplecov,
               ruby-thor,
               ruby-timecop,
               yard
Standards-Version: 4.4.0
Vcs-Git: https://salsa.debian.org/ruby-team/ruby-foreman.git
Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-foreman
Homepage: https://github.com/ddollar/foreman
Testsuite: autopkgtest-pkg-ruby
XS-Ruby-Versions: all

Package: ruby-foreman
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
Depends: ruby | ruby-interpreter,
         ruby-dotenv,
         ruby-thor (>= 0.19.1),
         ${misc:Depends},
         ${shlibs:Depends}
Description: Process manager for applications with multiple components
 Foreman is a process manager commonly used during development of
 multi-component applications. For production, it allows allow you to either
 run your application directly or export it to some other process management
 format (i.e. init system service files).
 .
 Foreman uses a file called Procfile, which is the same mechanism for declaring
 what commands are run by your application’s dynos on the Heroku platform. It
 follows the process model. You can use a Procfile to declare various process
 types, such as multiple types of workers, a singleton process like a clock, or
 a consumer of the Twitter streaming API.