Can't find credentials-smtp.env

[frisbee23]

sudo docker-compose build Couldn't find env file: /home/core/credentials-smtp.env

[juanluisbaptiste]

Fix your docker-compose.yml file and point it to the right location of your credentials-smtp.env for the postfix container.

[frisbee23]

ok, alright, i get it.

i expected your docker image works out of the box.

i tried creating that file, and it worked.

but then you use data container, and really you don't. i'll try my luck with some other maintainer. cheers, fil

On Tue, Feb 21, 2017 at 3:52 PM, Juan Luis Baptiste < notifications@github.com> wrote:

Fix your docker-compose.yml file and point it to the right location of your credentials-smtp.env for the postfix container.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/9#issuecomment-281366115, or mute the thread https://github.com/notifications/unsubscribe-auth/AVB-QjzLHO4Qpw1acUVZRRz0cZLOCGa8ks5revpBgaJpZM4MHaZw .

-- Philipp Knoll // +43 699 10485901 // frisbee23@gmail.com

[juanluisbaptiste]

None container will work out of the box, how could I provide a SMTP relay with a generic email account ? you should read the documentation first.

And what do you mean by "but then you use data container, and really you don't." ? both docker-compose.yml files use data containers.

Good luck finding another OTRS image, after you search docker hub you will notice that the only one being maintained is this one, and many others are forks of this one too.

[frisbee23]

man, you seem to be not interested in improving the user experience of your image. i guess thats why people needto fork it.

this conversation could have been an opportunity, but you seem to not have the time and patience.

you are right with data containers. i got once the error that volumes_from is decprecated. but then it worked. fyi.

https://hub.docker.com/r/ajeeth/otrs-itsm_auto/ worked for me. it's not as good as yours, but at least i could get it to run out of the box.

cheers!

On Tue, Feb 21, 2017 at 6:23 PM, Juan Luis Baptiste < notifications@github.com> wrote:

None container will work out of the box, how could I provide a SMTP relay with a generic email account ? you should read the documentation first.

And what do you mean by "but then you use data container, and really you don't." ? both docker-compose.yml files use data containers.

Good luck finding another OTRS image, after you search docker hub you will notice that the only one being maintained is this one, and many others are forks of this one too.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/9#issuecomment-281413678, or mute the thread https://github.com/notifications/unsubscribe-auth/AVB-QgVruuYb15EGWoQZXStanAXiZC2dks5rex13gaJpZM4MHaZw .

-- Philipp Knoll // +43 699 10485901 // frisbee23@gmail.com

[juanluisbaptiste]

None of those forks has gone anywhere, and this one has more than 17k pulls, wonder why ?

This is an open source project, so you are welcome to help improve it instead of complaining.

[juanluisbaptiste]

And an opportunity for what ? with this mediocre report that really doesn't say what you think needs improving ? please at least take an effort to do a quality report about your issues if you want developers to pay attention to you.

[frisbee23]

thats not the point. a oneliner could increase your pullcount constantly.

also suspicous that there are only four issues.

how you reply on other issues, also.

i guess you just dont want to be bothered.

dont tell me im welcome when all you answer is twisting words around

On Wed, 22 Feb 2017 at 16:55, Juan Luis Baptiste notifications@github.com wrote:

None of those forks has gone anywhere, and this one has more than 17k pulls, wonder why ?

This is an open source project, so you are welcome to help improve it instead of complaining.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/9#issuecomment-281710704, or mute the thread https://github.com/notifications/unsubscribe-auth/AVB-QvwrMKA59BlptigdMHc9XvjTzBz7ks5rfFplgaJpZM4MHaZw .

-- Philipp Knoll // +43 699 10485901 // frisbee23@gmail.com

[frisbee23]

the problem is not the report, but the messy docs that lead to a quick question from me

On Wed, 22 Feb 2017 at 16:57, Juan Luis Baptiste notifications@github.com wrote:

And an opportunity for what ? with this mediocre report that really doesn't say what you think needs improving ? please at least take an effort to do a quality report about your issues if you want developers to pay attention to you.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/9#issuecomment-281711245, or mute the thread https://github.com/notifications/unsubscribe-auth/AVB-Qkkiw3uV7pb05IAtn5DSFooFiGuVks5rfFrLgaJpZM4MHaZw .

-- Philipp Knoll // +43 699 10485901 // frisbee23@gmail.com

[juanluisbaptiste]

thats not the point. a oneliner could increase your pullcount constantly.

If you want to use an OTRS system on PRODUCTION you can't have an "out of the box experience", you NEED to configure some aspects of the installation, that's why when you do a new install of OTRS you have to go through a wizard to configure it.

And the container that you end up using has a lot of limitations and goes against docker best practices of running just one service per container. Also it will not work out of the box, it doesn't even install a email service, so you WILL have to do some configuration afterwards anyway, so what's your point ?

Do you think that's better an quicker to launch the container and then go through all the installation wizard and setup an external SMTP server than just writing a bunch of environment variables in a file and avoid all that?

also suspicous that there are only four issues.

Well I don't care if you don't believe there are only 4 issues, for me that speaks for it self of the quality and acceptance of my work.

i guess you just dont want to be bothered.

Any developer don't want to be bothered with bad quality reports that only come from not reading carefully the documentation. If you want to be taken serious then do your homework first and provide all the information needed to debug the issue. Your report was only a run issue that came from not carefully reading the documentation.

Here's a recommended reading so you can improve your bug reporting skills and avoid doing useless reports like this one that don't go anywhere (as you seem to be new to how open source development model works):

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Good luck !

[frisbee23]

from my first post in the issue it is clearly visible that i tried to just run the command you mentioned in the docs, and it doesnt work.

i just followed along the documentation, and it is missing a required step.

from my point of view you should mention in the docs, that it is required to copy the variables from the compose file to a new env file. it's as simple as that.

and/or put a template file into the git repo.

cheers

On Wed, Feb 22, 2017 at 5:57 PM, Juan Luis Baptiste < notifications@github.com> wrote:

thats not the point. a oneliner could increase your pullcount constantly.

If you want to use an OTRS system on PRODUCTION you can't have an "out of the box experience", you NEED to configure some aspects of the installation, that's why when you do a new install of OTRS you have to go through a wizard to configure it.

And the container that you end up using has a lot of limitations and goes against docker best practices of running just one service per container. Also it will not work out of the box, it doesn't even install a email service, so you WILL have to do some configuration afterwards anyway, so what's your point ?

Do you think that's better an quicker to launch the container and then go through all the installation wizard and setup an external SMTP server than just writing a bunch of environment variables in a file and avoid all that?

also suspicous that there are only four issues.

Well I don't care if you don't believe there are only 4 issues, for me that speaks for it self of the quality and acceptance of my work.

i guess you just dont want to be bothered.

Any developer don't want to be bothered with bad quality reports that only come from not reading carefully the documentation. If you want to be taken serious then do your homework first and provide all the information needed to debug the issue. Your report was only a run issue that came from not carefully reading the documentation.

Here's a recommended reading so you can improve your bug reporting skills and avoid doing useless reports like this one that don't go anywhere (as you seem to be new to how open source development model works):

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Good luck !

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/9#issuecomment-281730803, or mute the thread https://github.com/notifications/unsubscribe-auth/AVB-Qnpp2W-d0GNjVp4o7ENwYS3H8oVOks5rfGjtgaJpZM4MHaZw .

-- Philipp Knoll // +43 699 10485901 // frisbee23@gmail.com

[juanluisbaptiste]

The documentation says:

How to run it

_By default, when the container is run it will load a default vanilla OTRS installation (OTRSINSTALL=no) that is ready to be configured as you need.

And also points you to the documentation of the postfix container were it says:

How to run it

The following env variables need to be passed to the container:

SMTP_SERVER Server address of the SMTP server to use. SMTP_USERNAME Username to authenticate with. SMTP_PASSWORD Password of the SMTP user. SERVER_HOSTNAME Server hostname for the Postfix container. Emails will appear to come from the hostname's domain.

So as you can read, the documentation indeed tells you what to do. And if you had also read docker-compose documentation you should know that you can put env files on the docker-compose.yml file or in a separate file like I use on my example compose files.

This is my last answer to this as you clearly are just trying to justify your position instead of actually being constructive. Another recommended reading:

https://en.wikipedia.org/wiki/RTFM

[frisbee23]

exactly. no word about the .env file in your docs.

it's just bad usability.

have a pleasant life.

On Wed, 22 Feb 2017 at 19:10, Juan Luis Baptiste notifications@github.com wrote:

The documentation says:

How to run it

By default, when the container is run it will load a default vanilla OTRS installation (OTRS_INSTALL=no) that is ready to be configured as you need.

And also points you to the documentation of the postfix container were it says:

How to run it

The following env variables need to be passed to the container:

SMTP_SERVER Server address of the SMTP server to use. SMTP_USERNAME Username to authenticate with. SMTP_PASSWORD Password of the SMTP user. SERVER_HOSTNAME Server hostname for the Postfix container. Emails will appear to come from the hostname's domain.

So as you can read, the documentation indeed tells you what to do. And if you had also read docker-compose documentation you should know that you can put env files on the docker-compose.yml file or in a separate file like I use on my example compose files.

This is my last answer to this as you clearly are just trying to justify your position instead of actually being constructive. Another recommended reading:

https://en.wikipedia.org/wiki/RTFM

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/9#issuecomment-281752796, or mute the thread https://github.com/notifications/unsubscribe-auth/AVB-QsQFM88g-bxajEZ0A_JJwy-zfK0pks5rfHoogaJpZM4MHaZw .