Transferring aptly setup (database, config, etc.) to new machine...

571 views
Skip to first unread message

mikele...@gmail.com

unread,
Apr 29, 2015, 7:29:25 PM4/29/15
to aptly-...@googlegroups.com
I've currently got an aptly setup on my workstation that includes a local repo and snapshots that I publish to an AWS S3 bucket via a config file. Now I need to migrate my setup to a new workstation and I'm wondering what I need to do to keep everything working smoothly.

Can I get away with just copying my .aptly and .aptly.conf to the new machine or are there other things I need to do? Where is the database actually located? Is there anything I need to export? Let me know if more information is required to answer my question.

Apologies if I missed a writeup on this already. Thanks!

Andrey Smirnov

unread,
May 8, 2015, 8:00:27 PM5/8/15
to mikele...@gmail.com, aptly-...@googlegroups.com
Hi!

If you're publishing to S3, copying ~/.aptly folder should be enough. It contains both database and package files.

If you publish locally (to ~/.aptly/public), you should copy files preserving hard links.

So in your case it should be fine.

--
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-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mikele...@gmail.com

unread,
May 8, 2015, 8:12:24 PM5/8/15
to aptly-...@googlegroups.com, mikele...@gmail.com
Thanks for the reply, Andrey. This did indeed work for me. Although, an additional step I had to take was copying over my gpg private/public keys (cp -r ~/.gnupg).

It'd actually be great if Aptly could detect this problem itself (I think the error propagated from whatever Aptly was invoking underneath), and then offer some suggestions - but that might be too much to ask :)
Reply all
Reply to author
Forward
0 new messages