public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] user config provisioning
Date: Wed, 20 May 2015 23:06:41 +0200	[thread overview]
Message-ID: <555CF761.90307@xunil.at> (raw)


I am currently trying to slim down and minimize my own few machines.

Way too much customer servers out there so I'd like to keep it simple in
here at least.

This lead me to configuring and provisioning my machines via ansible.

The goals:

* make sure that my user exists
* roll out configs/dotfiles/git-repos/home-dir
* maybe roll out some system-configs as well (systemd-units, timers) /
... separate ansible-role, OT here

etc

I have set up and maintained quite a list of bash-aliases to access my
customer-servers in daily work.

Something like:

alias abcd-server='ssh -p 51023 174.183.26.11'  # demo only

This is based on ssh-pubkey-authentication, sure.

My questions:

* if I have a user X on each machine, should each userX@machine have its
own ssh-pubkey? Or is it OK to roll out the same ~/.ssh to all machines?

* same q for ~/.gnupg ...

I can deploy the pubkeys to the servers via ansible, sure.
But I would like to keep it simple. stupid.

;)


             reply	other threads:[~2015-05-20 21:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 21:06 Stefan G. Weichinger [this message]
2015-05-20 22:02 ` [gentoo-user] user config provisioning Alan McKinnon
2015-05-21 11:28   ` Stefan G. Weichinger
2015-05-21 13:10     ` Alan McKinnon
2015-05-21 14:00       ` Stefan G. Weichinger
2015-05-21  8:49 ` Paul Tobias
2015-05-21 13:13   ` Stefan G. Weichinger
2015-05-21 15:04     ` Stefan G. Weichinger
2015-05-21 15:41       ` Stefan G. Weichinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=555CF761.90307@xunil.at \
    --to=lists@xunil.at \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox