-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
107 lines (95 loc) · 4.43 KB
/
index.html
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
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<link href='https://fonts.googleapis.com/css?family=Chivo:900' rel='stylesheet' type='text/css'>
<link rel="stylesheet" type="text/css" href="/stylesheets/stylesheet.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/stylesheets/pygment_trac.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/stylesheets/print.css" media="print" />
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<title>tpkg: Application packaging and deployment</title>
</head>
<body>
<div id="container">
<div class="sidebar">
<strong>Documents:</strong>
<ul>
<li><a href="get_started.html">Get started</a></li>
<li><a href="configure.html">Configure</a></li>
<li><a href="package.html">Package</a></li>
<li><a href="third_party.html">Package 3rd party apps</a></li>
<li><a href="deploy.html">Deploy</a></li>
<li><a href="package_server.html">Package server</a></li>
<li><a href="reporting_server.html">Reporting server</a></li>
<li><a href="production.html">Production</a></li>
<li><a href="externals.html">Externals</a></li>
<li><a href="faq.html">FAQ</a></li>
<li><a href="develop/">Develop</a></li>
</ul>
</div>
<div class="center">
<div class="inner">
<header>
<h1>tpkg</h1>
<h2>Application packaging and deployment</h2>
</header>
<hr>
<section id="main_content">
<p>
tpkg is a tool for packaging and deploying applications. It is designed to
work alongside your operating system's packaging tool. The deployment
features in tpkg are designed to scale to deployments across hundreds or
thousands of systems.
</p>
<p>
The packaging features of tpkg work in a similar fashion as many OS
packaging tools like rpm, dpkg, SysV, etc, but with some additional
features. Many shops just use the OS packaging system for their local
applications, so why would you want to use a separate tool?
</p>
<ul>
<li>tpkg is cross platform, so although you may have two or three different
operating systems in your environment you can use a common tool to package
and deploy your applications on those systems.</li>
<li>Separating the packaging of applications from the base OS system ensures
that application packages and their dependencies don't interfere with the
functioning of the base OS. For example, your OS comes with Perl 5.6.1, but
your application needs 5.8.9. By using tpkg and installing your application
and the newer version of Perl in a isolated location you avoid any conflicts
with base OS utilities that use the OS copy of Perl.</li>
<li>tpkg supports encrypting some or all of the files in the package, so
your application package can contain secret files like SSL or SSH keys,
database passwords, etc.</li>
<li>tpkg supports dependencies both on other tpkg packages as well as native
packages, and tpkg handles dependency resolution and automatic dependency
installation of both tpkg and native dependencies.</li>
<li>tpkg supports external hooks that can be used to tie into a system
configuration management tool, allowing packages to request accounts,
NFS mounts, kernel settings, etc.</li>
<li>Local caching of packages allows for rapid rollbacks.</li>
<li>An optional ReportingServer allows you to see what packages are
installed on systems in a central location.</li>
</ul>
<p>
The deployment features of tpkg allow you to automate the installation,
upgrade or removal of packages across a large number of systems. Tpkg
handles SSH and sudo prompts that might be encountered in connecting to the
target systems. The parallelism of deployment operations can be adjusted so
that deployments can be done in a rolling fashion at the desired rate.
</p>
<p>
Try a <a href="getting_started.html">demo</a> of tpkg on your systems.
Check the <a href="faq.html">FAQ</a> for answers to additional questions.
</p>
</section>
</div>
</div>
<section id="downloads" class="clearfix">
<a href="https://github.com/tpkg" id="view-on-github" class="button"><span>View on GitHub</span></a>
</section>
</div>
</body>
</html>