Fpm Alternatives
Similar projects and alternatives to fpm
-
Homebrew-cask
🍻 A CLI workflow for the administration of macOS applications distributed as binaries
-
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
omnibus-ruby
Easily create full-stack installers for your project across a variety of platforms.
-
-
-
-
-
-
-
-
-
-
-
wayback-machine-downloader
Download an entire website from the Wayback Machine.
-
-
WriteFreely
A clean, Markdown-based publishing platform made for writers. Write together, and build a community.
-
-
neocities
Neocities.org - the web site. The entire thing. Yep, we're completely open source.
-
Reviews and mentions
-
Why is it so difficult for a software application team to support so many distributions via packaging? Is there no machinery to robotically package any application for any of the given major distributions? Why not?
A few years ago I jumped on the fpm train. You might need to couple it up with some scripts, but it greatly simplifies things.
-
Ask HN: How to publish command line tools?
I wrote a shell script, I'd like to make available for others to use. Scripting language ideally shouldn't matter. Users should not have to care what I used. I'd like to target users who want to easily install a new command line tool on Linux/Mac and receive updates, but preferably without the need to install another package manager.
There is the possibility to package it for many package managers, like https://github.com/jordansissel/fpm
Other possibilities would be npm (most people have it already installed), zsh plugins (limited user base), deno (rewrite your shell script in typescript - which is probably a good thing).
Any other ideas? What are you using?
-
More tips for packaging your Linux software with RPM
I use fpm which is a lot more flexible and friendly to multiple build systems.
-
Converting a tarball to RPM
Use the effing package manager. https://github.com/jordansissel/fpm
- Hack The Box: Amageddon - Write-up by Khaotic
-
pkger 0.4.0 released! RPM, DEB and PKG building tool that utilizes docker now with more features and bugs fixed
Exciting! How do you compare this project with FPM ? FPM has been my go to for years.
-
Why creating a debian package is a PITA?
Here is link number 1 - Previous text "fpm"
I don't make .debs for my own stuff often, so I find it easier to just use FPM which would make a .deb that would install, but wasn't necessarily an Officially CorrectTM deb with all the bells and whistles. Looks like it hasn't been updated in a while, though.
Just use fpm
- Which python framework is used by professional to make a desktop gui app ?
-
How to install Python/Django modules on production?
I use FPM (https://github.com/jordansissel/fpm) to build a .deb package, which I install using Ansible. The package includes a virtualenv with all the Python dependencies as well as all the static files. I use a set of Make tasks to automate building the app, setting up the venv, placing the static files, and making the .deb. I upload my packages to a reprepro package repository that I manage (if I could do it again, I might use Aptly instead). I then use Ansible to set up the package repository, install the package, and place config files. It was a lot of work to set up but the production environment is all automated.
-
Tiny Container Challenge: Building a 6kB Containerized HTTP Server
But there is a lot of work to be done before you can do the simple apt install. I (gladly) don't know how it is nowadays but before Dockerfiles/Docker creating your own packages according to the various standards was a pita. Most companies needed a 'packaging specialist/release engineer' role as most developers where not up to the task. Solutions like FPM[0] did help somewhat, but it was still hard when dealing with non-homogeneous environments. Containers solved that problem universally for all distributions.
-
What's the proper way to "update" packages downloaded and built from Git?
Part 1 of my plan might sound difficult but there are lots of things that can help with it, e.g. https://github.com/jordansissel/fpm
-
Ask HN: Is there an easy way to release a CLI program for all major platforms?
[1]: https://github.com/jordansissel/fpm
-
Blog with Markdown and Git, and degrade gracefully through time
After compiling the binary (with haskell-stack) I use fpm to package it up as a .deb (https://github.com/jordansissel/fpm).
I then scp the file into the pool directory on my server, and re-run a script that calls apt-ftparchive and regenerates the contents of the repo (https://manpages.debian.org/buster/apt-utils/apt-ftparchive....).
My web server hosts that directory with indexing enabled, but I don't use apache for it like most examples do. There's nothing special about it, it's just a directory tree built in a way that apt likes. (https://pkg.kamelasa.dev/). In fact, the entire configuration of the repo is visible there.
There's a step in the middle where I sign the packages with my GPG key, and the public key is available on Ubuntu's keyserver (http://keyserver.ubuntu.com/).
I don't need to run this workflow very often, as it'll take about 40 minutes to rebuild and push. But if I do update my SSG I know it'll end up in my debian repo with a version bump, so I'm happy.
On a second pipeline I can just do a simple 'add-apt-repository' and 'apt install'.
Stats
jordansissel/fpm is an open source project licensed under MIT-like which is not an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.