jiti-meet/debian/jitsi-meet-web-config.templ...

Template: jitsi-meet/cert-choice
Type: select
__Choices: Generate a new self-signed certificate, Let's Encrypt certificates, I want to use my own certificate
_Description: SSL certificate for the Jitsi Meet instance
 .
 Jitsi Meet is best to be set up with an SSL certificate.
 .
 Having no certificate, a self-signed one will be generated.
 In the case of using a self-signed certificate, only the web app will be available with some warnings, the mobile app will not connect.
 Self-signed certificates are not supported by JaaS (Jitsi as a Service).
 .
 Having a certificate signed by a recognised CA, it can be uploaded on the server and point its location.
 The default filenames will be /etc/ssl/--domain.name--.key for the key and /etc/ssl/--domain.name--.crt for the certificate.

Template: jitsi-meet/cert-path-key
Type: string
_Description: Full local server path to the SSL key file:
 The full path to the SSL key file on the server.
 If it has not been uploaded, now is a good time to do so.

Template: jitsi-meet/cert-path-crt
Type: string
_Description: Full local server path to the SSL certificate file:
 The full path to the SSL certificate file on the server.
 If you haven't uploaded it, now is a good time to upload it in another console.

Template: jitsi-meet/jvb-hostname
Type: string
_Description: The hostname of the current installation:
 The value for the hostname that is set in Jitsi Videobridge installation.

Template: jitsi-videobridge/jvb-hostname
Type: string
_Description: Hostname:
 The Jitsi Meet web config package needs the DNS hostname of your instance.

Template: jitsi-meet/jaas-choice
Type: boolean
_Description: Interested in adding telephony to your Jitsi meetings?
 You can easily add dialing in support to your meetings using JaaS (Jitsi as a Service).
 You need to:
  - have a certificate signed by a recognised CA or Let’s Encrypt on your deployment
  - sign in for JaaS at https://jaas.8x8.vc/components?host=${domain}

Template: jitsi-meet/email
Type: string
_Description: Enter your email:
 To successfully issue Let's Encrypt certificates:
 .
 You need a working DNS record pointing to this machine(for hostname ${domain})"
 .
 You need to agree to the ACME server's Subscriber Agreement (https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf)
 by providing an email address for important account notifications
-												Adds missing templates.

											
										
										
											2014-08-29 15:18:28 +00:00
+								Template: jitsi-meet/cert-choice
 								Type: select
-												feat: Adds LE choice when installing debian package. (#12154)

* feat: Adds LE choice when installing debian package.

* Update debian/jitsi-meet-web-config.templates

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>

* squash: Print in the console the JaaS link everytime.

* squash: Note that JaaS does not support self-signed certs.

* squash: Fix message.

* squash: Moves acme.sh stuff into a script, so it is easy to re-run.

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>
											
										
										
											2022-09-13 12:55:00 +00:00
+								__Choices: Generate a new self-signed certificate, Let's Encrypt certificates, I want to use my own certificate
-												Fixes lintian errors.

											
										
										
											2014-09-03 15:00:24 +00:00
+								_Description: SSL certificate for the Jitsi Meet instance
-												feat: Adds LE choice when installing debian package. (#12154)

* feat: Adds LE choice when installing debian package.

* Update debian/jitsi-meet-web-config.templates

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>

* squash: Print in the console the JaaS link everytime.

* squash: Note that JaaS does not support self-signed certs.

* squash: Fix message.

* squash: Moves acme.sh stuff into a script, so it is easy to re-run.

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>
											
										
										
											2022-09-13 12:55:00 +00:00
+								 .
-												Adds missing templates.

											
										
										
											2014-08-29 15:18:28 +00:00
+								 Jitsi Meet is best to be set up with an SSL certificate.
-												feat: Adds LE choice when installing debian package. (#12154)

* feat: Adds LE choice when installing debian package.

* Update debian/jitsi-meet-web-config.templates

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>

* squash: Print in the console the JaaS link everytime.

* squash: Note that JaaS does not support self-signed certs.

* squash: Fix message.

* squash: Moves acme.sh stuff into a script, so it is easy to re-run.

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>
											
										
										
											2022-09-13 12:55:00 +00:00
+								 .
-												Fixes lintian errors.

											
										
										
											2014-09-03 15:00:24 +00:00
+								 Having no certificate, a self-signed one will be generated.
-												feat: Adds jaas choice when installing.

											
										
										
											2022-08-26 19:52:03 +00:00
+								 In the case of using a self-signed certificate, only the web app will be available with some warnings, the mobile app will not connect.
-												feat: Adds LE choice when installing debian package. (#12154)

* feat: Adds LE choice when installing debian package.

* Update debian/jitsi-meet-web-config.templates

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>

* squash: Print in the console the JaaS link everytime.

* squash: Note that JaaS does not support self-signed certs.

* squash: Fix message.

* squash: Moves acme.sh stuff into a script, so it is easy to re-run.

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>
											
										
										
											2022-09-13 12:55:00 +00:00
+								 Self-signed certificates are not supported by JaaS (Jitsi as a Service).
 								 .
 								 Having a certificate signed by a recognised CA, it can be uploaded on the server and point its location.
 								 The default filenames will be /etc/ssl/--domain.name--.key for the key and /etc/ssl/--domain.name--.crt for the certificate.
-												Adds missing templates.

											
										
										
											2014-08-29 15:18:28 +00:00
 								Template: jitsi-meet/cert-path-key
 								Type: string
-												Fixes lintian errors.

											
										
										
											2014-09-03 15:00:24 +00:00
+								_Description: Full local server path to the SSL key file:
-												Adds missing templates.

											
										
										
											2014-08-29 15:18:28 +00:00
+								 The full path to the SSL key file on the server.
-												Fixes lintian errors.

											
										
										
											2014-09-03 15:00:24 +00:00
+								 If it has not been uploaded, now is a good time to do so.
-												Adds missing templates.

											
										
										
											2014-08-29 15:18:28 +00:00
 								Template: jitsi-meet/cert-path-crt
 								Type: string
-												Fixes lintian errors.

											
										
										
											2014-09-03 15:00:24 +00:00
+								_Description: Full local server path to the SSL certificate file:
-												Adds missing templates.

											
										
										
											2014-08-29 15:18:28 +00:00
+								 The full path to the SSL certificate file on the server.
 								 If you haven't uploaded it, now is a good time to upload it in another console.
-												Fixes purging configuration.

											
										
										
											2014-10-23 08:00:48 +00:00
 								Template: jitsi-meet/jvb-hostname
 								Type: string
 								_Description: The hostname of the current installation:
 								 The value for the hostname that is set in Jitsi Videobridge installation.
-												Updates meet default installation. Removes nginx dependency and adds openjdk-8 in order to activate multiplexing inside jvb and use its jetty to serve meet. Updates will not touch current configuration which will continue using nginx.

											
										
										
											2015-07-27 21:07:22 +00:00
-												Removes dependencies to other components.

Now the web app can be installed separately from jicofo and jitsi-videobridge, or can be installed on machine running nginx or apache. Currently only nginx will be configured and apache config is left to user. Later we can add and the apache config. Renames jitsi-meet to jitsi-meet-web (just the web content) and jitsi-meet-web-config (configuring jetty, nginx or apache). A new jitsi-meet package will be introduced, a meta package depending on jicofo, jvb and the current packages.

											
										
										
											2016-11-21 21:16:37 +00:00
+								Template: jitsi-videobridge/jvb-hostname
 								Type: string
 								_Description: Hostname:
 								 The Jitsi Meet web config package needs the DNS hostname of your instance.
-												feat: Adds jaas choice when installing.

											
										
										
											2022-08-26 19:52:03 +00:00
 								Template: jitsi-meet/jaas-choice
 								Type: boolean
 								_Description: Interested in adding telephony to your Jitsi meetings?
 								 You can easily add dialing in support to your meetings using JaaS (Jitsi as a Service).
 								 You need to:
 								  - have a certificate signed by a recognised CA or Let’s Encrypt on your deployment
 								  - sign in for JaaS at https://jaas.8x8.vc/components?host=${domain}
-												feat: Adds LE choice when installing debian package. (#12154)

* feat: Adds LE choice when installing debian package.

* Update debian/jitsi-meet-web-config.templates

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>

* squash: Print in the console the JaaS link everytime.

* squash: Note that JaaS does not support self-signed certs.

* squash: Fix message.

* squash: Moves acme.sh stuff into a script, so it is easy to re-run.

Co-authored-by: raluca8x8 <raluca.tocmag@8x8.com>
											
										
										
											2022-09-13 12:55:00 +00:00
 								Template: jitsi-meet/email
 								Type: string
 								_Description: Enter your email:
 								 To successfully issue Let's Encrypt certificates:
 								 .
 								 You need a working DNS record pointing to this machine(for hostname ${domain})"
 								 .
 								 You need to agree to the ACME server's Subscriber Agreement (https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf)
 								 by providing an email address for important account notifications