maildev VS docs

As I said before Maildev is a neat and easy to use SMTP server that is great for development since you can have your application act as though its really sending emails and have that intercepted directly and reviewed in a neat GUI application. It's a nice way to solve the problem of testing emails but you are certainly welcome to do something else, possible dangerous, like actually send emails from your development box :). Again, I want you to start thinking about chaining applications together as a cluster of single purpose containers, all talking to each other via simple conventions and environment variables (for example you might have noticed that the DB_HOST was the same as the name of the database container; Docker does a great job of offering simple conventions like that which really save a lot of setup headache.

This looks quite nice and lean, we started using https://github.com/maildev/maildev especially for the arm64 support.

Reading about maildev, it seems to be a STMP server for testing. I assume then, the problem is in the mail() function.

There are other options besides running a fully blown internal mail server. You could try https://github.com/maildev/maildev or https://github.com/mailhog/MailHog (no longer being developed but still working great) if it is enough for your use case.

I was able to implement a simple verification link that a new user can click to confirm their account. However, my implementation is only up to localhost environment using maildev.

In my case, I used docker-compose to do this, but please read accordingly. Of course, you can also use Docker commands to run it, and even if you don't have Docker environment, you can install and use it with npm command. For more information, please look at official document here .

I will recommend you review the documentation for the official Postgresql docker images which you can read here.

This is the full documentation for these images. Please note, this page has links to Docker official documents on volumes, etc., which are necessary to run images such as this.

We've just followed the official documentation to add a PostgreSQL database server. This will act as an application container, as our app will soon be depended on it. And in order to make sure that the database container is always started whenever we start our application container, we've added a new depends_on key to the app service and let it know which other service(s) it, well, depends on. This will make sure that the database server is up and running before the app. You may also have noticed that we've mounted volume to our database server's datapath a bit differently. This is known as "named volume". We'll discuss it a bit more in another part, it's not relevant to what we're learning here.

Nextcloud isn't hard to setup, follow the official doc https://github.com/docker-library/docs/blob/master/nextcloud/README.md

Looking at the setup for this (link here: https://github.com/docker-library/docs/blob/master/nextcloud/README.md), I am starting to understand a lot of the recent posts that we've seen & how much of a mess it still is :(

Coming back to nextcloud, the official readme of the nextcloud image has a few notes on how to set up both nextcloud versions.

Use the native command envstubst to replace the Auth Tokens in your Config File before starting NGINX. Example: https://github.com/docker-library/docs/tree/master/nginx#using-environment-variables-in-nginx-configuration-new-in-119

It's not clear why you want to split the web server (nginx) and the app (nextcloud). However, if you do have a good reason, you're in luck, they have a compose file that does just that: https://github.com/docker-library/docs/blob/master/nextcloud/README.md#base-version---fpm (version 2, but it'll work)