Setting up the email service in the UI is a goal. That requires the
ability to send configuration to action plugins instead of relying on
system properties.
Le 27/05/2015 23:51, Matt Wringe a écrit :
Would the SMTP setup not be something which is something we can
display
to the user in the UI? eg on first login we ask the admin to configure
it. If they skip this setup, then when they go to add an email alert we
have a modal which tells them they cannot add email alert until they
configure the SMTP.
Or did I miss something here with how the email service is setup?
On 27/05/15 05:14 PM, Jay Shaughnessy wrote:
>
> It's not totally clear what we want to do in Hawkular to configure the
> smtp server for use with the e-mail action plugin for alerts. OOB WFly
> is configured for smtp server localhost:25. This generally does not
> work in dev envs.
>
> So, we deploy the e-mail action plugin, we supply the e-mail address
> in Hawkular user registration, and then we just generate server log
> warnings when it doesn't work. It's easily remedied with a a manual
> edit. For us we can set it to the RH corp smtp server, which will
> work fine as long as you run from behind the VPN, or on the corp net.
>
> We could hardcode this into our Dist but I'm not sure if we want to
> publicize that host.
>
> Otherwise, a manual edit is required unless we provide for some sort
> of build-time command line prop to be applied to Dist by the build.
>
> Thoughts?
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev