Open Stream issueshttps://labs.creek.org/open/stream/-/issues2018-05-17T01:05:05Zhttps://labs.creek.org/open/stream/-/issues/8Confirm DNS resolution for Let's Encrypt2018-05-17T01:05:05ZTravisConfirm DNS resolution for Let's EncryptUse case:
1. Create VPS with an initial cloud-init script run on first boot.
1. Include variables for cloud-init: domain name and email.
1. At the same time, start creating a correct domain at Route 53 or wherever we (or they) are man...Use case:
1. Create VPS with an initial cloud-init script run on first boot.
1. Include variables for cloud-init: domain name and email.
1. At the same time, start creating a correct domain at Route 53 or wherever we (or they) are managing domains.
1. Use Node.js to display on the VPS (at port 7000) a page that says the HTTPS set-up helper message (see below).
1. Once the domain resolves, then set up Let's Encrypt.
1. Continue to monitor the HTTPS connection with Creek Stream Tools. Poll it every day to see if the stream is working. In general, poll the stream to see if the studio connection is active. Notify the Creek HQ if the stream is down, and notification will be sent to the user from which this stream was built.
### HTTPS Helper Page Idea
```
HTTPS SET-UP
Waiting for domain to be created: domain.goes.here
Once your domain is ready, come back to this page and [click here] to set up HTTPS later.
Ask a Creek support to set up your domain if you need help.
This "your own domain" method is super-useful and frees you from the burden of hosting-provider lock-in. [See why lock-in sucks, read this.]
Open Stream, for the win.
See tutorial here: https://creek.fm/articles/open-stream-https
```https://labs.creek.org/open/stream/-/issues/7Clean up icecast.xml2017-12-30T23:01:31ZTravisClean up icecast.xml* [ ] Remove deprecated options. Look at XRAY.fm's server for example.
* [ ] Check for deprecations on Icecast server by checking if the icecast.xml validates when restarting its process.
* [ ] Remove unnecessary commented-out options.* [ ] Remove deprecated options. Look at XRAY.fm's server for example.
* [ ] Check for deprecations on Icecast server by checking if the icecast.xml validates when restarting its process.
* [ ] Remove unnecessary commented-out options.TravisTravishttps://labs.creek.org/open/stream/-/issues/5Reliable automatic renewal with cron2017-11-28T19:56:34ZTravisReliable automatic renewal with cronNeed to make sure that the certbot auto-renewal cron script in `certbot.sh` actually works.
## Optional Idea: Log file?
Maybe add a log file write to the `--post-hook` in the cron command in `certbot.sh`. Then the results of the renewa...Need to make sure that the certbot auto-renewal cron script in `certbot.sh` actually works.
## Optional Idea: Log file?
Maybe add a log file write to the `--post-hook` in the cron command in `certbot.sh`. Then the results of the renewal will be printed to a log file so that we can confirm that it works.
However, then this log file would need to be deleted every 4 months or so, allowing the 90 days to be encompassed in the log file, but so that the log file doesn't get infinitely large.
Or, other solutions?TravisTravishttps://labs.creek.org/open/stream/-/issues/4Add the Stream Tools with Stats Collector2017-08-22T07:00:20ZTravisAdd the Stream Tools with Stats Collector...and move the stream tools stats collector to a separate "Stats Collector" and make it a part of the open source repos at /open/stats-collector (along with /open/stats-client)....and move the stream tools stats collector to a separate "Stats Collector" and make it a part of the open source repos at /open/stats-collector (along with /open/stats-client).TravisTravishttps://labs.creek.org/open/stream/-/issues/3Make sure that log files work2017-11-28T05:11:54ZTravisMake sure that log files workSometimes they stop getting written.
But this might have been fixed in Icecast-KH 2.4.0-kh5: **"use a separate thread for logging, prevents worker stalls in certain setups."**
```
2.4.0-kh5
8/5/2017
* use a separate thread for loggi...Sometimes they stop getting written.
But this might have been fixed in Icecast-KH 2.4.0-kh5: **"use a separate thread for logging, prevents worker stalls in certain setups."**
```
2.4.0-kh5
8/5/2017
* use a separate thread for logging, prevents worker stalls in certain setups.
* backward compatibile playlist archive setting fix.
* update IPv6 handling. This is really an internal update but allows for both IPv4/IPv6 listening sockets to be created from one listen-socket block. This allows for windows builds to have IPv6 as well.
* autodetect SSL connections on incoming sockets. No need for <ssl> in listen-socket now but is still there for compatability.
* add <ssl-private-key> in <paths> to allow for combined PEM or for separate SSL key/certificate files.
* select https/http URL in autogenerated m3u based on incoming request.
* minor update to windows service creation. No functional change
```TravisTravishttps://labs.creek.org/open/stream/-/issues/2Add MPEG-DASH2017-08-22T06:54:55ZTravisAdd MPEG-DASHFor those desktop systems that don't easily support HLS, but do support DASH.
DASH also has a really good, first-party JavaScript client. So that's a huge plus. HLS doesn't have that (but we should only connect to HLS on devices that su...For those desktop systems that don't easily support HLS, but do support DASH.
DASH also has a really good, first-party JavaScript client. So that's a huge plus. HLS doesn't have that (but we should only connect to HLS on devices that support it, anyway).
Example:
https://stackoverflow.com/questions/34322021/nginx-rtmp-module-and-mpeg-dashdash-industry-dash-jsTravisTravishttps://labs.creek.org/open/stream/-/issues/1Add HLS with nginx2021-04-10T19:25:27ZTravisAdd HLS with nginxWe should add HLS to this framework.
# Hints:
## Setting up nginx and compiling:
https://docs.peer5.com/guides/setting-up-hls-live-streaming-server-using-nginx/
## Transcoding from Icecast:
- https://github.com/arut/nginx-rtmp-modul...We should add HLS to this framework.
# Hints:
## Setting up nginx and compiling:
https://docs.peer5.com/guides/setting-up-hls-live-streaming-server-using-nginx/
## Transcoding from Icecast:
- https://github.com/arut/nginx-rtmp-module/issues/1022
- http://code.steadman.io/blog/using-nginx-icecast-and-mpc-to-create-a-cross-platform-radio-station/
Code (but use AAC, not FLV):
```
rtmp {
server {
listen 1935;
chunk_size 4096;
application radio {
live on;
meta off;
exec_pull /usr/local/bin/ffmpeg -i http://localhost:8100/stream -f flv rtmp://localhost/radio/stream;
}
}
}
```
### Except...
...except use AAC rather than FLV.TravisTravis