You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version: Query latest and stable version from backend.
API for Function Query: The official website provides an API to query the latest stable functionality. The SRS logs display the status of the functionality.
#2508
Closed
winlinvip opened this issue
Aug 5, 2021
· 0 comments
Live HLS: 3.0 stable version, 4.0 stable version, 5.0 development version.
Live HDS: 4.0 deprecated version, will be removed in 5.0.
Live DVR recording: 3.0 stable version, 4.0 stable version, 5.0 development version.
Live Origin server cluster: 3.0 stable version, 4.0 stable version, 5.0 development version.
Live Edge server cluster: 3.0 stable version, 4.0 stable version, 5.0 stable version.
Communication RTC: 4.0 development version, 5.0 development version.
RTC to RTMP conversion: 4.0 development version, 5.0 development version.
RTMP to RTC conversion: 4.0 development version, 5.0 development version.
RTC cluster: 5.0 development version.
RTC Simulcast: 5.0 development version.
GB28181: 4.0 development version, 5.0 development version.
SRT: 4.0 development version, 5.0 development version.
Windows: 5.0 development version.
......
These features have stability and lifecycle changes with different versions. If you carefully review the relevant information, you can know the status of each feature. However, this approach has a high threshold and is cumbersome. Why not provide an API query like the stable version query on the official website?
For example, when SRS starts, it not only includes its own version but also the features it has enabled.
HTTP/HTTPS GET https://api.ossrs.net/service/v1/releases?docker=1
When querying the version, the currently enabled feature (docker=1) has also been added. In the response, the corresponding status of the feature is returned ("docker":"stable").
Response
{
"docker": "stable"
}
This makes it convenient to know the status of the desired feature in the corresponding version.
Config
Configuration method, default enabled:
# Query the latest available version of SRS, write a log to notice user to upgrade.
# @see https://github.com/ossrs/srs/issues/2424
# Default: on
query_latest_version on;
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered:
winlinvip
changed the title
功能查询API:官网提供API查询最新的稳定功能,SRS打日志提示
功能查询API:官网提供API查询最新的稳定功能,SRS打日志显示功能状态
Aug 5, 2021
winlinvip
changed the title
功能查询API:官网提供API查询最新的稳定功能,SRS打日志显示功能状态
Version: Query latest and stable version from backend. 功能查询API:官网提供API查询最新的稳定功能,SRS打日志显示功能状态
Jul 10, 2023
winlinvip
changed the title
Version: Query latest and stable version from backend. 功能查询API:官网提供API查询最新的稳定功能,SRS打日志显示功能状态
Version: Query latest and stable version from backend.
API for Function Query: The official website provides an API to query the latest stable functionality. The SRS logs display the status of the functionality.
Jul 29, 2023
Currently, there are many major functions in SRS, such as:
These features have stability and lifecycle changes with different versions. If you carefully review the relevant information, you can know the status of each feature. However, this approach has a high threshold and is cumbersome. Why not provide an API query like the stable version query on the official website?
For example, when SRS starts, it not only includes its own version but also the features it has enabled.
When querying the version, the currently enabled feature (
docker=1
) has also been added. In the response, the corresponding status of the feature is returned ("docker":"stable"
).This makes it convenient to know the status of the desired feature in the corresponding version.
Config
Configuration method, default enabled:
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: