Creating local mirrors of multiple apt based packages using aptly

445 views
Skip to first unread message

Russell Sutherland

unread,
Aug 4, 2017, 10:24:18 AM8/4/17
to aptly-discuss
I've stumbled upon aptly and spent some time creating a local mirror. Looks quite good, flexible and thorough.

I have a need to mirror multiple packages locally. In my case: elastic, zabbix, wazuh etc...

From my initial reading and experimenting, aptly seems to create only one publishing point:

~/.aptly/public

So is aptly flexible enough to mirror more than one package. And if so, where are the publish points in terms of the local file system

Many thanks in advance.

Frederic Van Espen

unread,
Aug 4, 2017, 10:39:18 AM8/4/17
to Russell Sutherland, aptly-discuss
Hello Russell,

Sure, by default aptly mirrors the full repository. It is even possible to filter some specific packages from the mirror.

On the file system level, everything is kept in one pool, but you can also specify a prefix when publishing if you would like multiple pools to keep things tidy (e.g. ~/.aptly/public/elastic). Have a look at the documentation of the "aptly publish snapshot" command.

Cheers,

Frederic

--
You received this message because you are subscribed to the Google Groups "aptly-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aptly-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Russell Sutherland

unread,
Aug 4, 2017, 11:25:30 AM8/4/17
to aptly-discuss, ru...@quist.ca
Does aptly 1.0.1 support the filesystem:label:directory construct for aptly snapshot publish?

I think not.

$ aptly publish snapshot elastic-5.x filesystem:packages:elastic/5.x/deb
ERROR: unknown published storage format: filesystem:packages
To unsubscribe from this group and stop receiving emails from it, send an email to aptly-discus...@googlegroups.com.

Andrey Smirnov

unread,
Aug 8, 2017, 5:38:52 PM8/8/17
to Russell Sutherland, aptly-discuss
Russel, that's feature for upcoming 1.1.0 (still testing last bugfixes before releasing it)
Reply all
Reply to author
Forward
0 new messages