Re: [openstack-dev] [TripleO][UI] Port number for frontend app

2016-08-24 Thread Hugh Brock
On Wed, Aug 24, 2016 at 12:18 PM, Dmitry Tantsur wrote: > On 08/22/2016 08:08 AM, Honza Pokorny wrote: >> >> Hello folks, >> >> We've been using port 3000 for the GUI during development and testing. >> Now that we're working on packaging and shipping our code, we're >>

Re: [openstack-dev] [TripleO][UI] Port number for frontend app

2016-08-24 Thread Dmitry Tantsur
On 08/22/2016 08:08 AM, Honza Pokorny wrote: Hello folks, We've been using port 3000 for the GUI during development and testing. Now that we're working on packaging and shipping our code, we're wondering if port 3000 is still the best choice. Would 3000 conflict with any other services? Is

Re: [openstack-dev] [TripleO][UI] Port number for frontend app

2016-08-24 Thread Jiri Tomasek
On 22.8.2016 08:08, Honza Pokorny wrote: Hello folks, We've been using port 3000 for the GUI during development and testing. Now that we're working on packaging and shipping our code, we're wondering if port 3000 is still the best choice. Would 3000 conflict with any other services? Is

Re: [openstack-dev] [TripleO][UI] Port number for frontend app

2016-08-22 Thread Erno Kuvaja
On Mon, Aug 22, 2016 at 7:08 AM, Honza Pokorny wrote: > Hello folks, > > We've been using port 3000 for the GUI during development and testing. > Now that we're working on packaging and shipping our code, we're > wondering if port 3000 is still the best choice. > > Would 3000

Re: [openstack-dev] [TripleO][UI] Port number for frontend app

2016-08-22 Thread Matthias Runge
On 22/08/16 08:08, Honza Pokorny wrote: > Hello folks, > > We've been using port 3000 for the GUI during development and testing. > Now that we're working on packaging and shipping our code, we're > wondering if port 3000 is still the best choice. > > Would 3000 conflict with any other services?

[openstack-dev] [TripleO][UI] Port number for frontend app

2016-08-22 Thread Honza Pokorny
Hello folks, We've been using port 3000 for the GUI during development and testing. Now that we're working on packaging and shipping our code, we're wondering if port 3000 is still the best choice. Would 3000 conflict with any other services? Is there a better option? Thanks Honza Pokorny