2018-09-18 10:53:43 +02:00
|
|
|
.. raw:: html
|
|
|
|
|
|
|
|
<div id="banner"><a href="https://github.com/jcbrand/converse.js/blob/master/docs/source/theming.rst">Edit me on GitHub</a></div>
|
|
|
|
|
2021-05-06 11:44:16 +02:00
|
|
|
=============================
|
|
|
|
Starting up a dev environment
|
|
|
|
=============================
|
2018-09-18 10:53:43 +02:00
|
|
|
|
|
|
|
Installing the 3rd party dependencies
|
|
|
|
=====================================
|
|
|
|
|
|
|
|
We use development tools which depend on Node.js and npm (the Node package manager).
|
|
|
|
|
|
|
|
If you don't have Node.js installed, you can download and install the latest
|
|
|
|
version `here <https://nodejs.org/download>`_.
|
|
|
|
|
|
|
|
Alternatively you can `use your operating system's package manager to install
|
|
|
|
Node.js <https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions>`_.
|
|
|
|
|
|
|
|
Also make sure you have ``Git`` installed. `See here <http://git-scm.com/book/en/Getting-Started-Installing-Git>`_.
|
|
|
|
|
|
|
|
Now use ``git`` to check out the Converse repository:
|
|
|
|
|
|
|
|
::
|
|
|
|
|
2019-05-15 12:36:51 +02:00
|
|
|
git clone https://github.com/conversejs/converse.js.git
|
2018-09-18 10:53:43 +02:00
|
|
|
|
|
|
|
Now go into the repository checkout and run ``make dev`` in order to set up the
|
|
|
|
development environment.
|
|
|
|
|
|
|
|
::
|
2019-05-15 12:36:51 +02:00
|
|
|
|
2018-09-18 10:53:43 +02:00
|
|
|
cd converse.js
|
|
|
|
make dev
|
|
|
|
|
2019-05-15 13:03:13 +02:00
|
|
|
If you're using Windows, or don't have GNU Make installed, you can run the
|
|
|
|
following:
|
2018-09-18 10:53:43 +02:00
|
|
|
|
|
|
|
::
|
|
|
|
|
2019-05-15 13:03:13 +02:00
|
|
|
cd converse.js
|
|
|
|
npm install
|
|
|
|
npm run lerna
|
2018-09-18 10:53:43 +02:00
|
|
|
|
|
|
|
This will install the Node.js development tools and Converse's dependencies.
|
|
|
|
|
|
|
|
The front-end dependencies are those JavaScript files on which
|
|
|
|
Converse directly depends and which will be loaded in the browser as part of
|
|
|
|
the bundle in ``dist/converse.js`` (or ``dist/converse.min.js``).
|
|
|
|
|
2019-05-15 12:36:51 +02:00
|
|
|
To see the 3rd party dependencies (not just the front-end dependencies, but
|
2018-09-18 10:53:43 +02:00
|
|
|
also ones necessary for development tasks like making builds), take a look at
|
|
|
|
the list under the ``devDependencies`` in `package.json <https://github.com/jcbrand/converse.js/blob/master/package.json>`_.
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
After running ```make dev```, you should now have a new *node_modules* directory
|
|
|
|
which contains all the external dependencies of Converse.
|
|
|
|
If this directory does NOT exist, something must have gone wrong.
|
|
|
|
Double-check the output of ```make dev``` to see if there are any errors
|
|
|
|
listed. For support, you can ask in our chatroom: `dicuss@conference.conversejs.org <xmpp:discuss@conference.conversejs.org>`_.
|
|
|
|
|
|
|
|
If you don't have an XMPP client installed, follow this link to
|
|
|
|
`conversejs.org <https://conversejs.org/fullscreen#converse/room?jid=discuss@conference.conversejs.org>`_
|
|
|
|
where you can log in and be taken directly to the chatroom.
|
|
|
|
|
|
|
|
|
2019-02-25 14:18:05 +01:00
|
|
|
.. _`dependency-libsignal`:
|
|
|
|
|
2018-09-18 10:53:43 +02:00
|
|
|
Libsignal
|
|
|
|
---------
|
|
|
|
|
2021-05-06 11:44:16 +02:00
|
|
|
If you want OMEMO encryption, you need to load `libsignal <https://github.com/signalapp/libsignal-protocol-javascript>`_ separately in your page.
|
2018-09-18 10:53:43 +02:00
|
|
|
|
|
|
|
For example::
|
|
|
|
|
|
|
|
<script src="3rdparty/libsignal-protocol-javascript/dist/libsignal-protocol.js"></script>
|
|
|
|
|
|
|
|
The reason libsignal needs to be loaded separately is because it's released
|
|
|
|
under the `GPLv3 <https://github.com/signalapp/libsignal-protocol-javascript/blob/master/LICENSE>`_
|
|
|
|
which requires all other dependent JavaScript code to also be open sourced under the same
|
|
|
|
license. You might not be willing to adhere to those terms, which is why you
|
|
|
|
need to decide for yourself whether you're going to load libsignal or not.
|