Aptly: Owning Your Debian Distribution
aptly.info
aptly.info
Aptly is a godsend to people who want to run .deb repos, as previously the software was basically "run a full mirror" or "sucks to be you". Jordan Sissel (fpm author) once remarked that 'there is a lot of silly ceremony in managing .debs'. We were previously using reprepro, which was alright, but had the glaring flaw of only allowing one version of a package to live in the repo. No easy rollbacks or machines on different versions there.
Aptly is really flexible, and although it does have some corner cases or slightly unintuitive behaviour (to me), it has excellent documentation and is in heavy development. Kudos to you, smira.
https://github.com/sepulworld/aptly-vagrant
It also sets up a Jenkins server so you can test out some build jobs that interact with Aptly.
I am looking forward to Aptly's REST API. Also on the roadmap is the ability to manage Yum repositories.
Here's my solution to this. Love using .debs for distribution.
At the moment working on REST API for aptly which should allow similar simple publishing scenarios.
Sort of like a cross between Launchpad and Travis CI. If anyone's interested in trying it out, I'd love feedback.
I've been using the free plan at https://packagecloud.io for my debs (handles my rpms and gems too), and it's been working well so far.
The most-used tools for getting a package into your repo involve scp'ing the file to the repository server and running a command to update its index. It's nice to have a proper toolset to do this, but it's too bad I spend most of my time with YUM nowadays.
Docker is for deployment, it works in terms of graphs of filesystem images. The tools do slightly overlap in use case, but they operate in entirely different domains.
It wouldn't be unreasonable to mix both in the same project, but there is no hard rule for when this would be appropriate.
Not really, it's just a tar file with some metadata. Using fpm¹, making packages from a directory is extremely simple. I've been building internal packages from our different components, and the build script only has three or four lines. And besides, even Dockerfiles often use apt/yum.
This is a problem for Go programs, due to multiple unversioned (usually) dependencies on other Go libraries.
I'm not going to be building .debs for installation inside Docker containers (turtles all the way down) but I would still consider something like aptly for storing and managing any obscure dependencies that my applications might require, and for maintaining a mirror on the local network to speed up image builds.
With aptly you're still using your favorite Debian/Ubuntu distro, installing packages with apt-get and so on.
At the moment, you'd have to use an external configuration management system for actually defining your systemd services, etc.
One thing missing from Nix is ability to store passwords and the like in the nix store, and from what I understand this applies to NixOS as well as using Nix outside NixOS. For example, every file in the nix store is world readable.
>> Linux distribution is well-tested collection of packages carefully organized and supported by the vendor.
wat?
Does this sound better:
"Linux distribution is a well-tested collection of packages that are carefully organized and supported by the vendor."
In trunk branch, the markdown under content/ folder.
"Linux distributions are well-tested collections of packages …"
But for singular you need to qualify "Linux distribution":
"A Linux distribution is a well-tested collection of packages …"
And I'd probably say "by a vendor" instead of "by the vendor" as it's not clear you're talking about a specific vendor.
Also, the "a" is wrong in this:
"There’s a support for …"
This should be: "There is support for …", in other words: "Support exists for …". Support is non-countable (like water, peace or terrorism) in English.
As a rule of thumb:
* if it's non-countable, just leave it bare: "I bought water", "It has support", "This is murder". * if you're referring to a specific instance of something the audience knows about or you're going to qualify, use "the": "I bought the house [I previously told you about]", "I shot the gopher that kept digging up my lawn". * otherwise use "a": "I bought a house" (this is news to you), "I ran over a cat" (if you say "the cat", the listener would instantly think "which one?").
English is "fun".
Similarly in a sentence like "Why don't you and the family come up to the house sometime for tea.". "The house" substitutes for "our house". Now all you need to work out is whether tea is afternoon tea, a cup of tea, or an evening meal and if the offer is sincere. I gather the response is supposed to be "That would be lovely." rather than actually trying to arrange the proffered social meeting.
Saying "the" instead of "a" generally assumes a context that has either been established before during the conversation or outside of it.
Imagine a stranger telling you they "accidentally killed the koala". You'd be confused. Not that strangers telling you about exotic animals they accidentally killed wouldn't be confusing enough.
Like you say "the item" means there should be an antecedent [previous mention].
If someone said they'd "killed the koala" I'd assume it was a euphemism for something!!
Our author seems to consistently make the same mistake: there's a distinct lack of articles in the writing. Sprinkle some in, and things start to make sense:
> [A] Linux distribution is [a] well-tested collection of packages
> we would like to have [an] internal mirror of [a] package repository
> some packages are missing in [the] official distribution
> we would like to own [a] package repository, that is to have [a] package repository
> There are many tools to create [a] mirror of [the] Debian package repositories
… and so on. At any rate, this consistency suggests (to me, at least) that he's probably not a native English speaker; in fact, the writer is almost certainly Russian. There's a link to a sponsor, which has a Russian phone number, and if you click around enough, you can find his CV quite easily.
Not everyone on the Internet speaks English, however, enough people do that I could easily see it being beneficial to put your content in English. Who knows?
http://en.wikipedia.org/wiki/Article_%28grammar%29#Variation...
One of my old bosses was Bosnian Croat, dropped articles like crazy, and added them in the wrong places. She would run her important emails by me for article-fixing before sending them. She was still smarter than me and better at her job than I was. Turns out that mastery of the arbitrary rules of English article placement and choice isn't a very good indicator of intelligence or competence.