1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
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 (= 13),
gem2deb (>= 1),
rake,
ruby-bundler,
ruby-dotenv,
ruby-fakefs,
ruby-rr,
ruby-rspec,
ruby-simplecov,
ruby-timecop,
yard
Standards-Version: 4.7.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
Rules-Requires-Root: no
Package: ruby-foreman
Architecture: all
Depends: ${misc:Depends},
${ruby: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.
|
