using ignite web console

[neerajbhatt <ne...@gmail.com>]

I am trying to install ignite web console in one of our servers (linux)as
given in https://apacheignite-tools.readme.io/v1.9/docs/build-and-deploy

We will be accessing the web console from different windows machine browser

Do we need server ip address while building front end or back end as we
won't be hitting  http://localhost:9000 
but  http://<server ip address>:9000




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/using-ignite-web-console-tp12847.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: using ignite web console

[Andrey Novikov <an...@apache.org>]

Hi,

Note your are trying to use development mode in production!
To bind development web server to all interfaces on your linux machine you
need fix following file:
modules/web-console/frontend/gulpfile.babel.js/webpack/environments/development.js
like this
https://github.com/apache/ignite/blob/master/modules/web-console/frontend/gulpfile.babel.js/webpack/environments/development.js
or use sources from master branch.


Also web console may be started from prepared docker image:
https://hub.docker.com/r/apacheignite/web-console-standalone/



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/using-ignite-web-console-tp12847p12964.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: using ignite web console

[Neeraj Bhatt <ne...@gmail.com>]

Hi Denis

Thanks for information, ignite web agent default. properties details are
documented in the link you shared
Can you please give name of property files of back end /frontend which need
to be changed as this is not documented anywhere.

Thanks



On Tue, May 16, 2017 at 5:31 AM, Denis Magda <dm...@apache.org> wrote:

> Yes, you need to give the machine where the console is to be deployed a
> unique IP address so that it’s accessible from remote machines. Also you
> might need to tweak some of web agent’s configuration parameters if the
> console should be linked with a remote Ignite cluster:
> https://apacheignite-tools.readme.io/v2.0/docs/getting-
> started#section-ignite-web-agent
>
> —
> Denis
>
> > On May 15, 2017, at 6:11 AM, neerajbhatt <ne...@gmail.com>
> wrote:
> >
> > I am trying to install ignite web console in one of our servers (linux)as
> > given in https://apacheignite-tools.readme.io/v1.9/docs/build-and-deploy
> >
> > We will be accessing the web console from different windows machine
> browser
> >
> > Do we need server ip address while building front end or back end as we
> > won't be hitting  http://localhost:9000
> > but  http://<server ip address>:9000
> >
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/using-ignite-web-console-tp12847.html
> > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>

Re: using ignite web console

[Denis Magda <dm...@apache.org>]

Yes, you need to give the machine where the console is to be deployed a unique IP address so that it’s accessible from remote machines. Also you might need to tweak some of web agent’s configuration parameters if the console should be linked with a remote Ignite cluster:
https://apacheignite-tools.readme.io/v2.0/docs/getting-started#section-ignite-web-agent

—
Denis

> On May 15, 2017, at 6:11 AM, neerajbhatt <ne...@gmail.com> wrote:
> 
> I am trying to install ignite web console in one of our servers (linux)as
> given in https://apacheignite-tools.readme.io/v1.9/docs/build-and-deploy
> 
> We will be accessing the web console from different windows machine browser
> 
> Do we need server ip address while building front end or back end as we
> won't be hitting  http://localhost:9000 
> but  http://<server ip address>:9000
> 
> 
> 
> 
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/using-ignite-web-console-tp12847.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.