public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>,
	Hazmi Alfarizqi <[email protected]>,
	Hazmi Alfarizqi <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>
Subject: Re: [PATCH server-a001 v1 2/2] Install MySQL server
Date: Sun, 17 Apr 2022 20:26:47 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAOG64qNoHnXfxhx3vnYw7zNqoC6Jb6+wSRL=UnZokJ70v6Dr-Q@mail.gmail.com>

On 4/17/22 8:06 PM, Alviro Iskandar Setiawan wrote:
> On Sun, Apr 17, 2022 at 7:51 PM Ammar Faizi <[email protected]> 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 <[email protected]>
>> ---
> 
> 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

  reply	other threads:[~2022-04-17 13:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17 12:51 [PATCH server-a001 v1 0/2] Install net-tools and MySQL server Ammar Faizi
2022-04-17 12:51 ` [PATCH server-a001 v1 1/2] Install net-tools Ammar Faizi
2022-04-17 13:13   ` Alviro Iskandar Setiawan
2022-04-18 17:00   ` Hazmi Alfarizqi
2022-04-17 12:51 ` [PATCH server-a001 v1 2/2] Install MySQL server Ammar Faizi
2022-04-17 13:06   ` Alviro Iskandar Setiawan
2022-04-17 13:26     ` Ammar Faizi [this message]
2022-04-17 13:34       ` Alviro Iskandar Setiawan
2022-04-17 13:44         ` Ammar Faizi
2022-04-17 13:52           ` Alviro Iskandar Setiawan
2022-04-17 14:02             ` Ammar Faizi
2022-04-17 14:17               ` Alviro Iskandar Setiawan
2022-04-17 14:57     ` Ammar Faizi

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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