Postal
Less Overly Complicated install #3329
Replies: 6 comments 2 replies
|
I do want to make it clear, I love postal! I stopped using it 2 years ago because I did not have a need, very excited to get V3 working. I dont want to sound ungrateful, I greatly appreciate what you do with this project. |
|
I was looking at installing it using Incus OCI app containers but it has a hard requirement for docker. It is definitely an unusual install. |
|
@JAP42 Lets go: Frist of all, we look at this file I find that rather unpleasant:
this should be it, add clamav as docker? https://hub.docker.com/r/clamav/clamav, if needed? fixed config location? /opt/postal/config Remove runner (we can just use any other service to execute commands) Now to the script:
We can just copy the files from example! Caddyfile can be removed? Its just configured as an reverse proxy, we can simple use docker port mapping for this 80:5000. signing.key can created by hand or whether the server has not yet been initialized
Can be executed when the server is started for the first time by simply checking whether the server has not yet been initialized
docker compose up -d
just pull the new image Could also be done automatically on version change! Other commands: just call them in service. My first small analysis is finished and I'll see if I can implement it myself. |
|
As a best practice I would keep the reverse proxy. This will greatly limit the amount of probing the actual server receives. Plus you can setup SSL and IP limits easily. Just because the application produces a webpage does not mean it should be serving to clients. https://github.com/tiredofit/docker-postal/tree/main This was the version I used and contributed a little to for version 2. There's no reason not to build the whole postal app in a single image that is infinitely reproducible. Maybe separate the different workers and setup startup requirements. Database should be MariaDB, spam assassin and clamav are already containerized. Just drop in. The internal docker network makes configuration minimal. |
|
@JAP42 i use a reverse proxy. but it is rather internal and would not use the caddy file that is simply placed in a folder by the installation script. I am just of the opinion that a simple documentation is sufficient here instead of copying a caddy file in the installation script. But then only documented in the documentation that it exists at all. https://docs.postalserver.io/getting-started/installation#caddy. But I won't watch it until tomorrow. In general, however, it shouldn't be rocket science, as the installation script is more or less “unnecessary”. |
|
The installation script essentially builds containers locally one at a
time. All four of the containers it creates start from the same image. It's
just a lot of unnecessary overhead, but the way it's written right now you
can't get away from it. I thankfully have a dedicated server, so it was
easy to just spin up an extra VM to run this exclusively in, but it would
have fit so nicely in its own composed group on my existing web server VM.
…On Tue, Apr 8, 2025, 11:01 AM lublak ***@***.***> wrote:
@JAP42 <https://github.com/JAP42> i use a reverse proxy. but it is rather
internal and would not use the caddy file that is simply placed in a folder
by the installation script. I am just of the opinion that a simple
documentation is sufficient here instead of copying a caddy file in the
installation script. But then only documented in the documentation that it
exists at all.
https://docs.postalserver.io/getting-started/installation#caddy.
https://github.com/postalserver/install/blob/main/bin/postal#L321
The installation script is a bit strange. Copying a file for a service
that is then optional again. You could also use Traefik, for example.
But I won't watch it until tomorrow. In general, however, it shouldn't be
rocket science, as the installation script is more or less “unnecessary”.
—
Reply to this email directly, view it on GitHub
<#3329 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALRVNECHJGQNTL2PMBO2VVD2YPQF5AVCNFSM6AAAAABY7REEUKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZWGYZDAMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
the current setup process doesn't make it easy to set it up in environments such as Coolify (still cannot make it work with traefik) It would be better if migrations and config generation could be done all via environment variables and on the first container runs. |
|
tiredofit retired most repos. |
Uh oh!
There was an error while loading. Please reload this page.
Every version of Postal has been a really complex process that does not need to be as hard as it is. I helped maintain a Simple Docker Compose file for V2.
With V3 supposedly working in all containers I expected to see a much simpler install, but you are still putting pieces all over the place and make a confusing install.
I should be able to install this entire program by copying 2 tiny files, changing a few .env variables, and running
docker compose up -d, this should be a 5 minuet install.All reactions