Need to update the installation script for RoQ Back-end and Management console ?

8 views
Skip to first unread message

Sabri Skhiri

unread,
Nov 12, 2012, 8:14:39 AM11/12/12
to roq-me...@googlegroups.com
Hello,

I just checked out the roq-management console page and I saw a strange comment in the Readme.md:
"Just put the content of the repository at the root of your web server. Don't forget to load extjs by issuing git submodule init git submodule update while at the root of the repository."

Does it mean that the process to follow is well:
1. Follow the instruction on the roq backend readme.md: https://github.com/roq-messaging/roq-backend
2. Cloning the roq management console git repo: git clone https://github.com/roq-messaging/roq-web-console.git
3. typing git submodule init git submodule update at the root of the installation directory

Can you confirm ? or is the submodule directly cloned with the roq-backend ?

If it is confirmed, can we update the installation script that currently stops at the backend installation :https://github.com/roq-messaging/RoQ/blob/develop/GimmeRoQ.sh

#OPTIONAL : Install the backend management
#Clone Git repository
git clone git://github.com/roq-messaging/roq-backend.git >> $INSTALLDIR/roq.log 2>&1

cd roq-backend

git checkout develop >> $INSTALLDIR/roq.log 2>&1

#Node Packages installation
npm install >> $INSTALLDIR/roq.log 2>&1

Finally, we need instructions to launch the management console, something like:
1. Start RoQ instance (GCM and host manager)
2. Start node.js
3. Start the console by opening ....TODO

Thank you all,

Sabri.

Quentin Dugauthier

unread,
Nov 12, 2012, 8:22:10 AM11/12/12
to roq-me...@googlegroups.com
ExtJS is now a submodule of the WebConsole.
So the structure of submodules is 

| roq-backend
+-| web-console
  +-|ext-js

Honestly, I'm not sure whether you should issue two git submodule init (one at the roq-backend level and one at the web-console level) or if one at the roq-backend level is enough. I would think the former is the right one, but it's to double check.

Once everything is installed, you have to launch:
1. the GCM
2. the host manager
3. the backend (with the web-api parameter)
4. Point your browser to localhost:3000 and enjoy/report bugs.

Q.

Jehan Bruggeman

unread,
Nov 12, 2012, 8:52:28 AM11/12/12
to roq-me...@googlegroups.com
Hi Sabri,

All you have to do is follow roq-backend's instructions (with a small correction -- see below). You do not need to clone yourself the management console, it is a submodule of roq-backend.

  1. install RoQ and dependencies (this will install the necessary zeromq stuff)
  2. Download the latest tarball from develop
  3. extract it somewhere
  4. install nodejs and npm (currently, v0.6 will do. On ubuntu, packages with the same name exist)
  5. install dependencies. To do that, go into roq-backend folder and run:

    npm install
    
  6. fetch submodules. To do that, go into roq-backend folder and run:

    git submodule init
    git submodule update --recursive 
  7. Run the backend: "./launcher.js web-api"


The "--recursive" option should ensure extJS is also downloaded.

Jehan

Sabri Skhiri

unread,
Nov 12, 2012, 1:31:17 PM11/12/12
to roq-me...@googlegroups.com
OK thanks I will update the installation script.

Thanks !

Sabri Skhiri

unread,
Nov 17, 2012, 1:27:26 PM11/17/12
to roq-me...@googlegroups.com
I have upated the installation file, that works fine. However I managed to start node.js but not to see management console.
once I started the backedn with  "./launcher.js web-api", what should I do to open the management console ?
I have tried to open the index.html but it does not work, I have a blank page on firefox. Does it require chrome ?

Sabri.

Jehan Bruggeman

unread,
Nov 17, 2012, 1:31:59 PM11/17/12
to roq-me...@googlegroups.com

True, that information is missing. If I remember correctly, the server starts on localhost:3000 . Point your browser to that address and you should see the web UI!

Jehan

Sabri Skhiri

unread,
Nov 17, 2012, 4:09:57 PM11/17/12
to roq-me...@googlegroups.com
on localhost:3000 the same blank page on Firefox ...

Sabri.
Reply all
Reply to author
Forward
0 new messages