Received: from mail.server-residenz.com (mail.server-residenz.com [144.76.125.99])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id C7689781BD7
	for <~alpine/users@lists.alpinelinux.org>; Tue, 14 Jul 2020 08:23:17 +0000 (UTC)
Subject: Re: Alpine upgrades on a physical server
To: ~alpine/users@lists.alpinelinux.org
References: <364e26c9-9d9f-25ff-64a1-bd5b32e47e73@it-express.ru>
From: Andreas Heil <ah@linux-hq.de>
Message-ID: <463fbea7-fbea-ec30-268a-ad086c9f0e91@linux-hq.de>
Date: Tue, 14 Jul 2020 10:23:13 +0200
MIME-Version: 1.0
In-Reply-To: <364e26c9-9d9f-25ff-64a1-bd5b32e47e73@it-express.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: de-DE

Hi,

I've also running it on a ton of servers and had NEVER had a problem 
with it.

I'm just bumping the version in the repositories file with ansible and 
after that an 'apk upgrade -U -a' followed by a reboot.

-- 
Andreas


Am 13.07.20 um 17:31 schrieb Andrey Abramov:
> Hello!
>
> Is it ok to run alpine on a physical server?
> I am talking about upgrades especially - new versions release quite 
> frequently (and are supported only within a year), so how alpine 
> handles this kind of upgrades? (I mean 3.12 -> 3.13 -> 3.14 -> ....)
>