From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.88.87] (unknown [36.80.217.41]) by gnuweeb.org (Postfix) with ESMTPSA id D2C117E394; Sun, 17 Apr 2022 13:26:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1650202014; bh=v2MSwtNIiGEbgIJzUtxp5CuwtInwH3XPOVc03JKjrv8=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=EqUuwm131l6HJ3tufagxCcoBbHm7GxmumG6A2vgqP2jomoTkDij7Mst5zScziVLgN idJGeyI3HeWF4mBI2uH2h9CFfQr1FjuKntiXgQLJlPEUZaSMLrmi5dEDBPqCscAn/L 0kO9JXE62uY6FhyzU5XU63+WuOxiXnyuT03RxG2cYFnD0CYMqOoCqSMAy3Cfwa/E23 uXrBywLp8kWD52lkE2eP/pHynTivMZ0lBk1jf1Pj+2KfiK+0hv87os4R/OJZJoRevV UoKTOygSGsdX02N9/QApckXsKZBLkwg6bmJI5caMFt8lrCTax1N93fF0bhUXR7O/P/ cJsPAVBvXDHBQ== Message-ID: Date: Sun, 17 Apr 2022 20:26:47 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Content-Language: en-US To: Alviro Iskandar Setiawan Cc: GNU/Weeb Mailing List , Hazmi Alfarizqi , Hazmi Alfarizqi , Alviro Iskandar Setiawan References: <20220417125125.160068-1-ammarfaizi2@gnuweeb.org> <20220417125125.160068-3-ammarfaizi2@gnuweeb.org> From: Ammar Faizi Subject: Re: [PATCH server-a001 v1 2/2] Install MySQL server In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 4/17/22 8:06 PM, Alviro Iskandar Setiawan wrote: > On Sun, Apr 17, 2022 at 7:51 PM Ammar Faizi wrote: >> >> We will need a MySQL server as the database for: postfix, dovecot and >> mail accounts. This will give us mysql-server v8. >> >> Signed-off-by: Ammar Faizi >> --- > > This patch is lacking in MySQL preparation, like setting up user/pass, > port to be exposed, database, and whatnot. Instead of deferring many > things for next, why not include it in this patch? OK, it's reasonable to have the user setup at this point. I will do that in the v2. > Also, it needs persistent storage, container is temporary, but our > database is permanent??? This is not a Dockerfile problem, it's a container problem. Which is done at `docker run`. So there is no relevance with mounting host's directory. The change is about Dockerfile. And we don't use a docker-compose.yml here. I don't see the need to involve that. Yes? No? Comment? -- Ammar Faizi