Fork of GlowingBear, with a different login page pre-filling informations.
Find a file
Lorenz Hübschle-Schneider 07d706d825 Add a .editorconfig
2016-01-06 21:05:16 +01:00
3rdparty Update dependenices 2015-01-18 12:05:21 +01:00
assets Self-host app store badges to reduce number of connections 2015-11-01 12:56:40 +01:00
css add CSS to make spin icon 2015-12-14 15:49:44 +01:00
directives set a title on the send button 2015-12-19 15:47:49 +01:00
js Fixed a circular ref in date change messages 2016-01-04 19:58:32 -05:00
test fix #688 and provide a unit test 2015-12-01 21:31:12 +02:00
.editorconfig Add a .editorconfig 2016-01-06 21:05:16 +01:00
.gitignore Documentation; make test file executable, jshint tests, add a gitignore 2014-08-26 20:17:22 -04:00
.jshintrc Use strict 2014-09-07 16:55:18 +01:00
.travis.yml travis: upgrade to container-based infrastructure 2015-08-05 17:38:15 +02:00
bower.json Add some basic tests for filters 2015-01-03 11:20:04 -05:00
COPYING Add license information 2013-10-04 16:52:45 -04:00
index.html #725 Updated wording to include reference to openssl sha256 argument 2016-01-02 21:08:20 -05:00
manifest.json Tag version 0.5.0 2015-09-22 20:15:04 +02:00
manifest.webapp Tag version 0.5.0 2015-09-22 20:15:04 +02:00
package.json update karma and install some dependencies; fixes #696 2015-12-08 23:50:26 +02:00
README.md fixes regarding EmojiOne 2015-12-16 12:34:35 +01:00
run_tests.sh Documentation; make test file executable, jshint tests, add a gitignore 2014-08-26 20:17:22 -04:00
serviceworker.js implement on notification click 2015-12-22 14:40:01 +01:00
webapp.manifest.json Chrome WebApp now loads manifest 2015-12-20 14:52:13 +01:00

#A web client for WeeChat Build Status

Glowing Bear is a web frontend for the WeeChat IRC client and strives to be a modern interface. It relies on WeeChat to do all the heavy lifting and then provides some nice features on top of that, like embedding images, videos, and other content. The best part, however, is that you can use it from any modern internet device -- whether it's a computer, tablet, or smart phone -- and all your stuff is there, whereever you are. You don't have to deal with the messy technical details, and all you need to have installed is a browser or our app.

##Getting Started

Glowing Bear connects to the WeeChat instance you're already running (version 0.4.2 or later is required), and you need to be able to establish a connection to the WeeChat host from your device. It makes use of the relay plugin, and therefore you need to set up a relay. If you want to get started as quickly as possible, use these commands in WeeChat:

/relay add weechat 9001
/set relay.network.password YOURPASSWORD

Now point your browser to the Glowing Bear! If you're having trouble connecting, check that the host and port of your WeeChat host are entered correctly, and that your server's firewall permits incoming connections on the relay port.

Please note that the above instructions set up an unencrypted relay, and all your data will be transmitted in clear. Therefore, we strongly recommend that you set up encryption if you want to keep using Glowing Bear. We've written a detailed guide on how to set up a trusted secure relay for you.

You can run Glowing Bear in many ways: use it like any other webpage, as an app in Firefox (choose "Install app" on the landing page) or Chrome ("Tools", then "Create application shortcuts"), or a full-screen Chrome app on Android ("Add to homescreen"). We also provide an Android app that you can install from the Google Play Store, and a Firefox OS app in the Firefox Marketplace.

Android app on Google PlayFirefox OS app in the Firefox Marketplace

##Screenshots

Running as Chrome application in a separate window on Windows and as Android app:

Glowing bear screenshot

##How it Works

What follows is a more technical explanation of how Glowing Bear works, and you don't need to understand it to use it.

Glowing Bear uses WeeChat directly as its backend through the relay plugin. This means that we can connect to WeeChat directly from the browser using WebSockets. Therefore, the client does not need a special "backend service", and you don't have to install anything. A connection is made from your browser to your WeeChat, with no services in between. Thus, Glowing Bear is written purely in client-side JavaScript with a bit of HTML and CSS.

##FAQ

  • Can I use Glowing Bear to access a machine or port not exposed to the internet by passing the connection through my server? No, that's not what Glowing Bear does. You can use a websocket proxy module for your webserver to forward /weechat to your WeeChat instance though. Here are some pointers you might find helpful for setting this up with nginx or apache.
  • How does the encryption work? TLS is used for securing the connection if you enable encryption. This is handled by your browser, and we have no influence on certificate handling, etc. You can find more detailed instructions on how to communicate securely in the "encryption instructions" tab on the landing page. A detailed guide on setting up a trusted secure relay is available here.

##Development

###Setup Getting started with the development of Glowing Bear is really simple, partly because we don't have a build process (pure client-side JS, remember). All you have to do is clone the repository, fire up a webserver to host the files, and start fiddling around. You can try out your changes by reloading the page.

Here's a simple example using the python simple web server:

git clone https://github.com/glowing-bear/glowing-bear
cd glowing-bear
python -m SimpleHTTPServer

Now you can point your browser to http://localhost:8000!

Remember that you don't need to host Glowing Bear yourself to use it, you can just use our hosted version powered by GitHub pages, and we'll take care of updates for you. Your browser connects to WeeChat directly, so it does not matter where Glowing Bear is hosted.

If you'd prefer a version hosted with HTTPS, GitHub serves that as well with an undocumented, not officially supported (by GitHub) link. Be careful though, it might break any minute. Anyway, here's the link: secret GitHub HTTPS link.

You can also use the latest and greatest development version of Glowing Bear at https://latest.glowing-bear.org/.

###Running the tests Glowing Bear uses Karma and Jasmine to run its unit tests. To run the tests locally, you will first need to install npm on your machine. Check out the wonderful nvm if you don't know it already, it's highly recommended.

Once this is done, you will need to retrieve the necessary packages for testing Glowing-Bear (first, you might want to use npm link on any packages you have already installed globally):

$ npm install

Finally, you can run the unit tests:

$ npm test

Or the end to end tests: $ npm run protractor

Note: the end to end tests assume that a web server is hosting Glowing Bear on localhost:8000 and that a WeeChat relay is configured on port 9001.

##Contributing

Whether you are interested in contributing or simply want to talk about the project, join us at #glowing-bear on freenode!

We appreciate all forms of contributions -- whether you're a coder, designer, or user, we are always curious what you have to say. Whether you have suggestions or already implemented a solution, let us know and we'll try to help. We're also very keen to hear which devices and platforms Glowing Bear works on (or doesn't), as we're a small team and don't have access to the resources we would need to test it everywhere.

If you wish to submit code, we try to make the contribution process as simple as possible. Any pull request that is submitted has to go through automatic and manual testing. Please make sure that your changes pass the Travis tests before submitting a pull request. Here is how you can run the tests:

$ ./run_tests.sh

We'd also like to ask you to join our IRC channel, #glowing-bear on freenode, so we can discuss your ideas and changes.

If you're curious about the projects we're using, here's a list: AngularJS, Bootstrap, Underscore, favico.js, Emoji provided free by Emoji One, and zlib.js. Technology-wise, WebSockets are the most important part, but we also use local storage, the Notification Web API, and last (but not least) Apache Cordova for our mobile app.