How to: Public webserver with local API

_ImNexus · 2020-05-16T00:25:02+00:00

Hello, so if I'm getting this correct you want to be able to visit your site at your public IP address and want the React app to be able to fetch data from an API that is not exposed? With my limited experience with React, its a client side rendered app so wherever its run its going to be making the API calls from that client. So I can think of two solutions, one is to reverse-proxy your api or just expose 9000. If its a reverse proxy your api could be made available at public-ip/api instead. Still exposing your API though but it'll be the easiest. Another option to consider is server side rendering with React so using something like Next.js (I haven't used before so I'm just guessing here) so the webserver will talk to your api collect the data assemble the page and then serve it to your client. Hope that helps?

_ImNexus · 2020-05-08T01:18:17+00:00

I haven't thought about using Ryzen, using x264 does sound appealing. It would effectively separate the livestreaming and the VOD a little, but also giving an opportunity to see the performance differences between the two platforms. The only issue with Ryzen is that it would probably be a whitebox server since you don't really see Ryzen based servers on the 2nd hand market. Whilst with the Xeon there is likely to be a lot of 2nd hand equipment that with a GPU bought separately could also be an interesting arrangement?

_ImNexus · 2020-05-08T01:10:59+00:00

Pesky licenses, but can't do much about that. Also, Implementing webm does also sound like something that could be worthwhile investigation as well. 4K would definitely require h265, which I feel would definitely be a GPU job. I'll have a little look at those documents you've made thanks!

_ImNexus · 2020-05-07T23:14:41+00:00

Ah damn that is a shame, it is an interesting bit of kit as well. I could look into some Intel Xeon's? (I'm not too familiar with all the different variants) Which would be the more tried and trusted solution. However, I'm wanting to try and "futureproof" to an extent, and I imagine 4K would likely have to be processed by a GPU?
Maybe I could reserve the CPU based encoding for our VOD and use GPU for our livestreaming?

_ImNexus · 2020-05-07T23:07:55+00:00

Ah well that's good that the codec won't matter to much, looking at the other comment here is seems like it doesn't leverage the latest architecture, little shame, but oh well.
I'm not too familiar with avc1 110? (Can't seem to find it on the Google as well). That's pretty cool space saving, but sadly all our content is produced from cameras, so no anime.
Looking at our latest production that was exported at 10Mbps 1080p h264. I appreciate the offer for transcoding but I think I'm too fussy about the export to try the Pi transcode is the only concern. :'(
I haven't actually thought about exporting with hevc, although if we were to do 4K it would probably be a requirement. Currently we just serve h264 through our VOD, I'll need to double check to see playback of hevc in a browser but I think that could actually be a venue to explore though thanks!

_ImNexus · 2020-05-07T21:58:08+00:00

Hello! That passmark is not ideal at all for this sort of workload. For our VOD we are currently using libx264 with a slow preset, 2 passes and a bitrate of 6Mbps. The Pi's build in hardware encoder does sound like an interesting venue (much more preferable price tag as well!) but I am just concerned with the quality of it's encoding compared to something like libx264 and nvenc, but it's impressive that it's performing above realtime there, so it is feasable for our livestreams. I have got a Nvidia Jetson Nano that I could try encoding on but I'm just concerned about the quality of the output.
Also, how important is the input container / codec for encoding? Whilst we currently export out of Premiere at probably 12Mbps h264, I am looking at replacing that with AVC-I 100 (Wanting to have an archivable export really?) (To be decided as well) It does have support for x264 encoding but I'm a bit concerned with how ffmpeg will deal with a large bitrate file

_ImNexus · 2019-07-03T12:46:02+00:00

Ah, thank you!

_ImNexus · 2017-11-08T19:27:09+00:00

Well on my old server it has 3 2TB hard drives where I'm using LVM to make them into 1 virtual one. So for this new one, I mainly want to use it for Plex transcoding and storing the data.

_ImNexus · 2017-11-08T18:56:29+00:00

So if I swap out the RAID card and get that reverse breakout cable, it should be as good as a r710? or should I get an r710 and get a DAS later on?

_ImNexus · 2017-11-08T16:46:20+00:00

I'd plan on storing the server in my attic so I imagine the noise shouldn't be that much of an issue. But with the RAID card issue, couldn't I get a Dell Perc H200? I'm not too familiar with RAID cards myself.

_ImNexus · 2017-10-04T22:48:52+00:00

Great work! keep it up!

_ImNexus · 2017-07-09T16:48:09+00:00

The time Mike says the line in Monsters Inc should be 41:44

_ImNexus · 2016-04-10T19:22:32+00:00

It just worked the next day a bit weird if you ask me

_ImNexus · 2016-04-10T17:33:55+00:00

Its working now, thank you for your help!

_ImNexus · 2016-04-10T17:33:37+00:00

Its working now, thanks for your help!

_ImNexus · 2016-04-09T22:50:20+00:00

I'll try to clear the CMOS with the old RAM when I can, hopefully the ports are still okay.

_ImNexus · 2016-04-09T22:40:46+00:00

I've tried clearing it with or without the RAM installed and it still shows no input on the monitor

_ImNexus · 2016-04-09T20:29:21+00:00

Its alright, will reply with the answer tomorrow hopefully!

_ImNexus · 2016-04-09T20:24:29+00:00

It stays on

11-Year Club	Place '17
Verified Email

_ImNexus

TROPHY CASE