Consolidate frontend & backend configs about owncast HOT 7 CLOSED

After clarifying with @gabek how this would work, I think it currently makes sense to put this all the info into one file. I like the idea of having set restricted types of these fields which would allow us to have a more consistent and controllable look and feel across Owncast instances.

And in this case, if we ever need to add a new configurable frontend field, all instances would need to be updated to use it because the config structure has changed and the frontend markup will have most likely changed.

from owncast.

@graywolf336 Heads up, this is changed in master, so now both frontend and backend has a single config location.

from owncast.

Ok, it now looks like this:

"socialHandles": [
{
"platform": "twitter",
"url": "http://twitter.com/owncast"
},
{
"platform": "instagram",
"url": "http://instagram.biz/owncast"
},
{
"platform": "facebook",
"url": "http://facebook.gov/owncast"
},
{
"platform": "tiktok",
"url": "http://tiktok.cn/owncast"
},
{
"platform": "soundcloud",
"url": "http://soundcloud.com/owncast"
}

from owncast.

..On that note, can I make a request to add a couple fields to the config? 😁

• allow for different logo image sizes,

logo: {
  small: "logo64x64.png",
  large: "logo256x256.png",
},
...

• string to the "extra" static info content.md field.. Perhaps something along the lines of:

{
  ...
  extraUserInfoFileName: "/static/content-example.md",
}

(Sorry I can't think of a better name for that right now)

from owncast.

On it!

from owncast.

Awesome!! 🎉

from owncast.

@gabek One more request, regarding the social list in the config-
Can you make that list an array, that would end up looking like this:
[
{platform: "facebook", url: "http.."},
{platform: "instagram", url: "http.."}
]

This will let users order their social acts by priority.

from owncast.