Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
galene
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
galene
Commits
3398e929
Commit
3398e929
authored
Jul 04, 2021
by
Juliusz Chroboczek
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Tweaks to README.
Fixes the instructions for compling under Windows.
parent
6143f53c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
11 deletions
+12
-11
README
README
+12
-11
No files found.
README
View file @
3398e929
...
@@ -9,7 +9,7 @@ You will need Go 1.13 or later (type `go version`). Then do:
...
@@ -9,7 +9,7 @@ You will need Go 1.13 or later (type `go version`). Then do:
On Windows, do
On Windows, do
set CGO_ENABLED=0
set CGO_ENABLED=0
go build -ldflags=
'-s -w'
go build -ldflags=
"-s -w"
## Set the server administrator credentials
## Set the server administrator credentials
...
@@ -69,13 +69,14 @@ should also allow UDP traffic to the TURN port, and UDP traffic to
...
@@ -69,13 +69,14 @@ should also allow UDP traffic to the TURN port, and UDP traffic to
ephemeral (high-numbered) ports (or whatever is configured using the
ephemeral (high-numbered) ports (or whatever is configured using the
`-udp-range` option).
`-udp-range` option).
If your server is behind NAT, then the NAT must forward, at the very
If your server is behind NAT (which is not recommended), then the NAT must
least, port 8443 to your server. Ideally, you should configure an
forward, at the very least, port 8443 to your server. Ideally, you should
external TURN server (see *ICE Servers* below) on a host that is not
configure an external TURN server (see *ICE Servers* below) on a host that
behind NAT. If that is not possible, then you should forward port 1194 in
is not behind NAT. If that is not possible, then you must use a NAT that
addition to port 8443, and you should add the option `-turn 203.0.113.1:1194`
supports hairpinning, you must forward port 1194 in addition to port 8443,
to Galène's command line, where `203.0.113.1` is your NAT's external
and you will need to add add the option `-turn 203.0.113.1:1194` to
(global) IPv4 address.
Galène's command line, where `203.0.113.1` is your NAT's external (global)
IPv4 address.
## Cross-compile for your server
## Cross-compile for your server
...
@@ -95,7 +96,7 @@ For a BeagleBone or a Raspberry Pi 2 or later:
...
@@ -95,7 +96,7 @@ For a BeagleBone or a Raspberry Pi 2 or later:
CGO_ENABLED=0 GOOS=linux GOARCH=arm GOARM=7 go build -ldflags='-s -w'
CGO_ENABLED=0 GOOS=linux GOARCH=arm GOARM=7 go build -ldflags='-s -w'
For a 64-bit ARM board (Olimex Olinuxino-A64, Pine64, etc.):
For a 64-bit ARM board (Olimex Olinuxino-A64, Pine64, etc.)
or server
:
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -ldflags='-s -w'
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -ldflags='-s -w'
...
@@ -116,7 +117,7 @@ a certificate, install it in the files `data/cert.pem` and `data/key.pem`:
...
@@ -116,7 +117,7 @@ a certificate, install it in the files `data/cert.pem` and `data/key.pem`:
ssh galene@server.example.org
ssh galene@server.example.org
sudo cp /etc/letsencrypt/live/server.example.org/fullchain.pem data/cert.pem
sudo cp /etc/letsencrypt/live/server.example.org/fullchain.pem data/cert.pem
sudo cp /etc/letsencrypt/live/server.example.org/key.pem data/key.pem
sudo cp /etc/letsencrypt/live/server.example.org/
priv
key.pem data/key.pem
sudo chown galene:galene data/*.pem
sudo chown galene:galene data/*.pem
sudo chmod go-rw data/key.pem
sudo chmod go-rw data/key.pem
...
@@ -332,7 +333,7 @@ If you prefer to use coturn's `use-auth-secret` option, then the
...
@@ -332,7 +333,7 @@ If you prefer to use coturn's `use-auth-secret` option, then the
[
[
{
{
"
U
rls": [
"
u
rls": [
"turn:turn.example.com:443",
"turn:turn.example.com:443",
"turn:turn.example.com:443?transport=tcp"
"turn:turn.example.com:443?transport=tcp"
],
],
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment