[jitsi-dev] jitsi-meet gulp/bower/npm automated build


#1

Hi All,

The code i discussed on the call today is available here:

https://github.com/chriswendt/jitsi-meet-gulp-bower-express

It’s not fully complete and likely has a few issues here and there and is not up-to-date with the current jitsu-meet, but if someone wants to continue with it, or if the build system updates can be used, feel free. If people are excited about it, perhaps I could be motivated to try update and to work on it further.

Let me know what you think.

-Chris


#2

Just a note, the latest greatest in automated build systems, seems to be webpack, might be another one to consider.

···

On Nov 9, 2015, at 10:42 PM, Chris Wendt <chris@chriswendt.net> wrote:

Hi All,

The code i discussed on the call today is available here:

https://github.com/chriswendt/jitsi-meet-gulp-bower-express

It’s not fully complete and likely has a few issues here and there and is not up-to-date with the current jitsu-meet, but if someone wants to continue with it, or if the build system updates can be used, feel free. If people are excited about it, perhaps I could be motivated to try update and to work on it further.

Let me know what you think.

-Chris


#3

Hi Chris,

Thank you very much for sharing this! it looks very nicely organized and we’re going to have a closer look at it. express.js on the server side is very cool and we would probably want to have it, if we didn’t want to keep the existing server side-less architecture.

Thank you!

···

-
George

On Nov 9, 2015, at 9:42 PM, Chris Wendt <chris@chriswendt.net> wrote:

Hi All,

The code i discussed on the call today is available here:

https://github.com/chriswendt/jitsi-meet-gulp-bower-express

It’s not fully complete and likely has a few issues here and there and is not up-to-date with the current jitsu-meet, but if someone wants to continue with it, or if the build system updates can be used, feel free. If people are excited about it, perhaps I could be motivated to try update and to work on it further.

Let me know what you think.

-Chris
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Hi George,

Thanks.

The express part is definitely not required per say, however, it just was easier because node/express works nicely with npm start command, so that was a slight advantage from a development flow/gulp auto start/recompile.

I believe the express part is really only handling the room to URL mapping that nginx and now i suspect jetty is handling.

-Chris

···

On Nov 11, 2015, at 10:52 AM, George Politis <gp@jitsi.org> wrote:

Hi Chris,

Thank you very much for sharing this! it looks very nicely organized and we’re going to have a closer look at it. express.js on the server side is very cool and we would probably want to have it, if we didn’t want to keep the existing server side-less architecture.

Thank you!

-
George

On Nov 9, 2015, at 9:42 PM, Chris Wendt <chris@chriswendt.net <mailto:chris@chriswendt.net>> wrote:

Hi All,

The code i discussed on the call today is available here:

https://github.com/chriswendt/jitsi-meet-gulp-bower-express

It’s not fully complete and likely has a few issues here and there and is not up-to-date with the current jitsu-meet, but if someone wants to continue with it, or if the build system updates can be used, feel free. If people are excited about it, perhaps I could be motivated to try update and to work on it further.

Let me know what you think.

-Chris
_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

My company has a custom web app UI built on top of Jitsi-meet (pulling in the non-UI modules). We use a gulp build with jspm/systemjs (similar to webpack) for module management. And then we use gulp-webserver<https://github.com/schickling/gulp-webserver> to serve our custom web app during development. It supports adding proxies and middleware so it should be possible to set it up to do the room name url mapping as well as proxying the bosh traffic. Our build includes watch and live reload functionality. I would recommend using something like webpack/jspm to make it easier to bundle various types of resources (css, html templates, js) into the app (or use browserify-css like was mentioned in the call). One cool thing about jspm is that it gives you a common interface for managing npm, bower, and github dependencies.

I might be able to lend some help toward this effort.

Devin

···

From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of Chris Wendt
Sent: Wednesday, November 11, 2015 6:29 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] jitsi-meet gulp/bower/npm automated build

Hi George,

Thanks.

The express part is definitely not required per say, however, it just was easier because node/express works nicely with npm start command, so that was a slight advantage from a development flow/gulp auto start/recompile.

I believe the express part is really only handling the room to URL mapping that nginx and now i suspect jetty is handling.

-Chris

On Nov 11, 2015, at 10:52 AM, George Politis <gp@jitsi.org<mailto:gp@jitsi.org>> wrote:

Hi Chris,

Thank you very much for sharing this! it looks very nicely organized and we’re going to have a closer look at it. express.js on the server side is very cool and we would probably want to have it, if we didn’t want to keep the existing server side-less architecture.

Thank you!

-
George

On Nov 9, 2015, at 9:42 PM, Chris Wendt <chris@chriswendt.net<mailto:chris@chriswendt.net>> wrote:

Hi All,

The code i discussed on the call today is available here:

https://github.com/chriswendt/jitsi-meet-gulp-bower-express

It’s not fully complete and likely has a few issues here and there and is not up-to-date with the current jitsu-meet, but if someone wants to continue with it, or if the build system updates can be used, feel free. If people are excited about it, perhaps I could be motivated to try update and to work on it further.

Let me know what you think.

-Chris
_______________________________________________
dev mailing list
dev@jitsi.org<mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org<mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

This email message is for the sole use of the intended recipient(s) and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, copying, disclosure or dissemination is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.