@@ -14,9 +15,7 @@
@@ -14,9 +15,7 @@
- A self contained OBS -> FTL -> WebRTC live streaming server. Comprised of 3 parts once configured anyone can achieve sub-second OBS to the browser livestreaming
-
-
+ A Self-Contained WebRTC streaming server designed to achieve sub-second browser livestreaming
View Demo
@@ -27,51 +26,32 @@
+I will be fleshing out the roadmap in the coming days. As of right now I want to get this to a point where it is
+as close to other live streaming services as possible. If there are any features that you want to see then feel
+free to suggest them!
-### Built With
+See the [open issues](https://github.com/GRVYDEV/Project-Lightspeed/issues) for a list of proposed features
+(and known issues).
-- Rust
-- Golang
-- React
+## Architecture
-### Components
+Lightspeed Ingest listens on port 8084 which is the port used by the FTL protocol. Upon receiving a connection it completes the FTL handshake and negotiates a port (this is currently bugged however and defaults to 65535). Once the negotiation is done Lightspeed WebRTC listens on the negotiated port (in the future Lightspeed WebRTC will listen on the loopback interface so the ingest has more control on what packets we accept) and relays the incoming RTP packets over WebRTC. Lightspeed React communicates via websocket with Lightspeed WebRTC to exchange ICE Candidates and once a connection is established the video can be viewed.
-- [Lightspeed Ingest](https://github.com/GRVYDEV/Lightspeed-ingest)
-- [Lightspeed WebRTC](https://github.com/GRVYDEV/Lightspeed-webrtc)
-- [Lightspeed React](https://github.com/GRVYDEV/Lightspeed-react)
+#### Diagram
+Here is a diagram that outlines the current implementation and the future implementation that I would like to achieve. The reason I want the packets relayed from Ingest to WebRTC on the loopback interface is so that we have more control over who can send packets. Meaning that when a DISCONNECT command is recieved we can terminate the UDP listener so that someone could not start sending packets that we do not want
-## Discord
-We now have a [Discord](https://discord.gg/UpQZANPYmZ) server! This is a great way to stay up to date with the project and join in on the conversation! Come stop by!
+
@@ -120,7 +98,13 @@ each repo however I will include them here for the sake of simplicity.
In order to run Lightspeed, [Golang](https://golang.org/doc/install), [Rust](https://www.rust-lang.org/tools/install), and [npm](https://www.npmjs.com/get-npm) are required. Additionally the Rust repo requires a C compiler. If you get a `linker cc not found` error then you need to install a C compiler.
-### Installation
+### Project Structure
+
+Sample Text
+
+## Installation
+
+### Manual
#### Lightspeed Ingest
@@ -163,9 +147,69 @@ Some of our awesome community members have written their own installers for Ligh
- [Ubuntu Installer](https://github.com/GRVYDEV/Project-Lightspeed/tree/main/contrib/ubuntu_installer)
+---
+
+
+### Docker
+
+Install [Docker](https://docs.docker.com/get-docker/) and [docker-compose](https://docs.docker.com/compose/install/).
+
+See the `.env` file to configure per your needs. At minimum, you need to set `WEBSOCKET_HOST`. The stream key will be
+generated automatically on boot, and change each restart, unless you set a static one.
+
+### Development
+
+Use `docker-compose up` to start all containers at once and monitor the logs. When you are happy it is working you can
+move to running detached.
+
+### Run Detached (background)
+
+Use `docker-compose up -d` to start all containers detached to have them run in the background.
+
+Use `docker ps` to verify uptime, port forwarding, etc.
+
+You can also use `docker-compose logs -f` to follow the logs of all the containers, and press `CTRL` + `C` to stop
+following but leave the containers running.
+
+### Build Images manually
+
+For development purposes you can choose to build the containers locally instead of Docker Hub. Uncomment the `build:`
+in the docker-compose.yaml. Configure the `context:` to be the path where you have cloned the respective respository
+([React](https://github.com/GRVYDEV/Lightspeed-react), [WebRTC](https://github.com/GRVYDEV/Lightspeed-webrtc), or
+[Ingest](https://github.com/GRVYDEV/Lightspeed-ingest)). For example, create a base folder and clone each repostiory
+there as such:
+
+```
+mkdir Lightspeed
+git clone ...
+git clone ...
+git clone ...
+---
+./Lightspeed # base folder
+ Project-Lightspeed/ # you are here
+ Lightspeed-react/
+ Lightspeed-ingest/
+ Lightspeed-webrtc/
+
+```
+
+Run `docker-compose build` to build the local container images. If you change the source code you will need to run again.
+You can run rebuild an individual container via `docker-compose build lightspeed-react`.
+
+
-## Usage
+## Configuration
+
+### Environment Variables
+
+Sample Text
+
+### Firewall
+
+Sample Text
+
+### CLI Usage
#### Lightspeed Ingest
@@ -221,59 +265,25 @@ The above will serve the build folder on port 80.
View Lightspeed in your web browser by visiting http://hostname or http://your.ip.address.here
+### Additional Notes
----
-
-
-## Docker
-
-Install [Docker](https://docs.docker.com/get-docker/) and [docker-compose](https://docs.docker.com/compose/install/).
-
-See the `.env` file to configure per your needs. At minimum, you need to set `WEBSOCKET_HOST`. The stream key will be
-generated automatically on boot, and change each restart, unless you set a static one.
-
-### Development
-
-Use `docker-compose up` to start all containers at once and monitor the logs. When you are happy it is working you can
-move to running detached.
-
-### Run Detached (background)
-
-Use `docker-compose up -d` to start all containers detached to have them run in the background.
+Sample Text
-Use `docker ps` to verify uptime, port forwarding, etc.
+---
-You can also use `docker-compose logs -f` to follow the logs of all the containers, and press `CTRL` + `C` to stop
-following but leave the containers running.
+## Streaming
-### Build Images manually
-
-For development purposes you can choose to build the containers locally instead of Docker Hub. Uncomment the `build:`
-in the docker-compose.yaml. Configure the `context:` to be the path where you have cloned the respective respository
-([React](https://github.com/GRVYDEV/Lightspeed-react), [WebRTC](https://github.com/GRVYDEV/Lightspeed-webrtc), or
-[Ingest](https://github.com/GRVYDEV/Lightspeed-ingest)). For example, create a base folder and clone each repostiory
-there as such:
-
-```
-mkdir Lightspeed
-git clone ...
-git clone ...
-git clone ...
----
-./Lightspeed # base folder
- Project-Lightspeed/ # you are here
- Lightspeed-react/
- Lightspeed-ingest/
- Lightspeed-webrtc/
-
-```
+#### Stream Key
-Run `docker-compose build` to build the local container images. If you change the source code you will need to run again.
-You can run rebuild an individual container via `docker-compose build lightspeed-react`.
+We are no longer using a default streamkey! If you are still using one please pull from master on the Lightspeed-ingest
+repository. Now, by default on first time startup a new streamkey will be generated and output to the terminal for you.
+In order to regenerate this key simply delete the file it generates called `hash`. In a Docker context we will work to
+make the key reset process as easy as possible. Simply copy the key output in the terminal to OBS and you are all set!
+This key WILL NOT change unless the `hash` file is deleted.
----
+
-## Streaming From OBS
+### OBS
By default, since we are using the FTL protocol, you cannot just use a Custom server. You will need to edit
your `services.json` file. It can be found at:
@@ -313,16 +323,6 @@ After restarting OBS you should be able to see your service in the OBS settings
---
-### Stream Key
-
-We are no longer using a default streamkey! If you are still using one please pull from master on the Lightspeed-ingest
-repository. Now, by default on first time startup a new streamkey will be generated and output to the terminal for you.
-In order to regenerate this key simply delete the file it generates called `hash`. In a Docker context we will work to
-make the key reset process as easy as possible. Simply copy the key output in the terminal to OBS and you are all set!
-This key WILL NOT change unless the `hash` file is deleted.
-
-
-
## Help
This project is still very much a work in progress and a lot of improvements will be made to the deployment process.
If something is unclear or you are stuck there are two main ways you can get help.
@@ -332,14 +332,7 @@ If something is unclear or you are stuck there are two main ways you can get hel
-## Roadmap
-
-I will be fleshing out the roadmap in the coming days. As of right now I want to get this to a point where it is
-as close to other live streaming services as possible. If there are any features that you want to see then feel
-free to suggest them!
-See the [open issues](https://github.com/GRVYDEV/Project-Lightspeed/issues) for a list of proposed features
-(and known issues).
## Bugs
@@ -359,11 +352,15 @@ Any contributions you make are **greatly appreciated**.
4. Push to the Branch: ``git push origin feature/AmazingFeature``
5. Open a Pull Request
+#### Templates
+- [ISSUE TEMPLATE](contributing/ISSUES.md)
+- [PULL REQUEST TEMPLATE](contributing/PULL-REQUESTS.md)
+
## License
-Distributed under the MIT License. See `LICENSE` for more information.
+Distributed under the MIT License. See [LICENSE.md](LICENSE.md) for more information.
diff --git a/contributing/ISSUES.md b/contributing/ISSUES.md
new file mode 100644
index 0000000..b25e5ba
--- /dev/null
+++ b/contributing/ISSUES.md
@@ -0,0 +1,24 @@
+
+
+#### Issue Description
+* When Issue Happens
+* Steps To Reproduce
+
+#### System Information (Only fill in applicable fields)
+* Browser Name, Version
+* Docker Version
+* Linux Version
+* Stable / Pre-Release
+
+#### Error Message
+
+```
+If relevant, paste your error message here
+```
+
+#### Screenshot
diff --git a/contributing/PULL-REQUESTS.md b/contributing/PULL-REQUESTS.md
new file mode 100644
index 0000000..9993f49
--- /dev/null
+++ b/contributing/PULL-REQUESTS.md
@@ -0,0 +1,21 @@
+## Pull Request template
+Please, go through these steps before you submit a PR.
+
+1. Make sure that your PR is not a duplicate.
+2. If not, then make sure that:
+
+ a. You have done your changes in a separate branch. Branches should have descriptive names that start with either the `fix/` or `feature/` prefixes. Good examples are: `fix/signin-issue` or `feature/issue-templates`.
+
+ b. You have a descriptive commit message with a short title (first line).
+
+ c. You have only one commit (if not, squash them into one commit).
+
+3. **After** these steps, you're ready to open a pull request.
+
+ a. Give a descriptive title to your PR.
+
+ b. Provide a description of your changes.
+
+ c. Put `closes #XXXX` (where xxxx is the issue number) in your comment to auto-close the issue that your PR fixes (if such).
+
+**PLEASE REMOVE THIS TEMPLATE BEFORE SUBMITTING**