Life is far, far saner if you can make a package. Things like FPM make this sort of thing so easy (e.g. turn a tarball into an RPM) you need a very good reason not to.
On 30 April 2012 01:39, Shoujin Wang <shoujinw...@gmail.com> wrote: > I have some old packages which was not in standard RPM/DEB packages. > We have our own deployment process likes this: > All the packages are in a directory, which likes the following: > /opt/package/pkg-aa/ > /readme.txt > /install.sh > /...... > /..... > > I want the puppet helps like this: > 1). Put pkg-aa on puppet master; > 2). puppet agent download the package from master, and run "install.sh". > > And I expect to have "file" and "service" types to handle configuration file > and restart service. > > Is there a way to accomplish 1) and 2) efficiently? > > Regards, > Autumn Wang > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/0M7FsS_Np2IJ. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
