cbcf8d4794
* Fix the http port used not in sync with what is logged * Actually fix the logging race condition * Move the router logging to the router package |
||
|---|---|---|
| .github | ||
| .vscode | ||
| build | ||
| config | ||
| controllers | ||
| core | ||
| data | ||
| doc/api | ||
| examples | ||
| geoip | ||
| logging | ||
| metrics | ||
| models | ||
| router | ||
| static | ||
| test | ||
| utils | ||
| webroot | ||
| yp | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| .prettierignore | ||
| CODE_OF_CONDUCT.md | ||
| config-default.yaml | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| openapi.yaml | ||
| pkged.go | ||
| README.md | ||
Take control over your content and stream it yourself.
Explore the docs »
View Demo
·
Use Our Server for Testing
·
FAQ
·
Report Bug
Table of Contents
- About the Project
- Getting Started
- Use with your broadcasting software
- Video storage and distribution options
- Building from source
- License
- Contact
About The Project
In 2020 the world changed when everyone become stuck in their homes, looking for creative outlets to share their art, skills and themselves from inside their bedroom.
This created an explosion of live streaming on Facebook Live, YouTube Live, Instagram, and Twitch. These services provided everything they needed, an easy way to live stream to the world, and a chat for users to be a part of their community.
That's when I wanted a better option for people. Something you could run yourself and get all the functionality of these services, where you could live stream to an audience and and allow them to take part in the chat, just like they've been used to on all the other services. There should be a independent, standalone Twitch in a Box.
Keep in mind that while streaming to the big social companies is always free, you pay for it with your identity and your data, as well as the identity and data of every person that tunes in. When you self-host anything you'll have to pay with your money instead. But running a self-hosted live stream server can be done for as cheap as $5/mo, and that's a much better deal than selling your soul to Facebook, Google or Amazon.
Getting Started
The goal is to have a single service that you can run and it works out of the box. Visit the Quickstart to get up and running.
Configuration
Many aspects can be adjusted and customized to your preferences. Read more about Configuration to update the web UI, video settings, and more.
Web interface + chat
Owncast includes a web interface to your video with built-in chat that is available once you start the server.
The web interface was specifically built to be editable by anybody comfortable tweaking a web page. It's not bundled or transpiled into anything, it's just HTML + Javascript + CSS that you can start editing.
Read more about the features provided and how to configure them in the web documentation.
Use with your existing broadcasting software
In general Owncast is compatible with any software that uses RTMP to broadcast to a remote server. RTMP is what all the major live streaming services use, so if you’re currently using one of those it’s likely that you can point your existing software at your Owncast instance instead.
OBS, Streamlabs, Restream and many others have been used with Owncast. Read more about compatibility with existing software.
Video storage options
Two ways of storing and distributing the video are supported.
- Locally via the Owncast server.
- S3-compatible storage.
Local file distribution
This is the simplest and works out of the box. In this scenario video will be served to the public from the computer that is running the server. If you have a fast internet connection, enough bandwidth alotted to you, and a small audience this may be fine for many people.
S3-Compatible Storage
Instead of serving video directly from your personal server you can use a S3 compatible storage provider to offload the bandwidth and storage requirements elsewhere.
Read more detailed documentation about configuration of S3-compatible services.
Building from Source
- Ensure you have the gcc compiler configured.
- Install the Go toolchain.
- Clone the repo.
git clone https://github.com/owncast/owncast go run main.go pkged.gowill run from source.- Point your broadcasting software at your new server and start streaming.
There is also a supplied Dockerfile so you can spin it up from source with little effort. Read more about running from source.
Bundling in latest admin from source
The admin ui is built at: https://github.com/owncast/owncast-admin it is bundled into the final binary using pkger.
To bundle in the latest admin UI:
- Install pkger.
go install github.com/markbates/pkger/cmd/... - From the owncast directory run the packager script:
./build/admin/bundleAdmin.sh - Compile or run like above.
go run main.go pkged.go
License
Distributed under the MIT License. See LICENSE for more information.
Contact
Project chat: Join us on Rocket.Chat if you want to contribute, follow along, or if you have questions.
Gabe Kangas - @gabek@mastodon.social - email gabek@real-ity.com
Project Link: https://github.com/owncast/owncast