Worried about Review Process

[BarryCarlyon]

@AnD4D

Also the last step: “Change the https://theURLtoMyEBS to the URL of your now running EBS” confused us, as it doesn’t tell us where we’re meant to change the url, let alone where the URL is meant to be aimed at, especially as we appeared to be running it via our command prompt.

The EBS, is essentially a server that runs as a web address you define.

I cannot tell you what the URL is as I don’t know where you are hosting your EBS from.

Additionally all communications need to be over SSL, so you need a SSL certificate. I generate mine from letsencrypt.

@AnD4D

Yeah, we’ve taken your example, and followed the guide as best as we could. We assume “In the ebs folder copy config_sample.json to config.json” is asking us to rename the file, but we weren’t 100% sure.

Copy or rename, either way you need to change the value in the file, to where ever you put/host your EBS at.

BarryCarlyon/twitch_profile_extension/blob/main/extension/config_sample.js

var my_ebs = ‘https://theURLtoMyEBS’;

becomes

var my_ebs = ‘mywebsite.com is available for purchase - Sedo.com’;

Of where ever your EBS is hosted at

@AnD4D

Gotta say, for an example code, they’ve made it incredibly hard to reverse engineer, with variables being converted into other variables, then finally getting called. I understand that for an actual program, but it seems like a strange choice for a tutorial/example.

It’s an example I wrote which assumes you have basic knowledge of javascript and how to make http requests to the API. So it shows how to bind existing knowledge together to make a working extension. It lacks comments as I’ve not gone back to add more comments everywhere.

The front end script literally does one thing,

• grab the JWT
• post the JWT to the EBS
• grab the response from the EBS
• draw a table from that response

The server is a bit more indepth and has a few more comments.

• Generates an App access token to use
• Waits for a HTTP Post
• Grabs the JWT and if valid,
• Takes the userID and app access token to call the Twitch API
• Pass the whole json blob back to the front end

So if you are building your EBS in nodeJS you can just cherry pick out the whole server but probably do something different at line 124 after you’ve got the users profile from the Twitch API

@AnD4D

We then shifted our attention to the colour changing example within the Dev Rig, and managed to get that working, but we’re hitting walls regarding how to change the path of the backend.js.

Yeah example illustrates how to pass pubsub messages from one place to another without a EBS iirc correctly. An example that generally wouldn’t be used in production.

@AnD4D

Instead, I’m getting the feeling I need to have an actual program running constantly, which is even further outside of my wheelhouse.

Depends what language you write your EBS in.

If it’s written in PHP, the PHP-FPM would be running all the time.
If it’s nodeJS then your server.js (like my example) would be running all the time

For example.

It needs to always be on/able to respond as you don’t know when it will be called.

An EBS is essentially a website.