Le 11/04/2020 à 12:15:12+0200, Martin Alfke a écrit Hi everyone.
> Thanks for the answer. > > I would like to have your point of view on how you install some software. > > > > Long time (in IT meaning) most of the software installation meaning run > > some rpm, apt, and put a config file. > > That process is still considered best practice. I agree, but I'm not the guy who write the code of the software I need to install > > That's something very easy to do with puppet. > > > > Currently lot of software need something, IMHO, more easy for the user, but > > much more hard to put inside a puppet. For example, installing some nodejs > > software means to > > > > install nodejs > > run npm > > > > Don't do that as a Puppet developer. > Let the developers build complete software packages with all dependencies > built into. > e.g. gem bundler directory must be part of the application package. > > Building packages can easily be done by using fpm > (https://github.com/jordansissel/fpm/wiki). > No special Debian or RPM knowledge required. I will look for that very closely, Thanks for the tips. I didn't know this one. > > > > (Ok I know it's not secure...) but well... > > The same pattern: let the wget | sudo bash command run on a dev platform or a > container and build a package. Ok, so if I'm correct here is the workflow : Using some gitlab/github + fpm, I run all the script from the software vendor, and built a package. Using puppet install that package. Put my config file in puppet Each time I need a upgrade I rerun my git pull/push CI to build the package Am I correct ? Regards. -- Albert SHIH Observatoire de Paris xmpp: [email protected] Heure local/Local time: Wed 15 Apr 2020 03:47:44 PM CEST -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20200415135118.GH3219%40io.chezmoi.fr.
