I jus want to make an panel to send commands to my chatbot, but i cannot even run the Hello world
i followed all steps inTwitch Extensions Developer Rig:
-clone repository
-install node.js, yarn program
run the command “yarn install” by windows cmd on clone repository root.
-created a extension on twitch
-edit the windows host file
-made a configuration file with the variables
And finaly i run the Developer Rig
Now i am trying the hello world but i dont how to make it work
-clone extensions-hello-world
-run the command “yarn install” by windows cmd on clone repository root.
-root directory i must run the command node services/frontend
Thanks for the help, but i guess i am wasting my and yours time.
I have done many softwares as 3D third person shooter using Unity3d, made support helpers using IBM Watson, made web pages using java/ajax/oracle for many industries here on Brazil only following the documentation, tutorials and videos. But i cant even develop a simple panel on twitch.
I will wait until twitch have more material to help new developers from zero to hero.
The curl command should work on Windows too if you combine it all on one line. \ on linux and mac commandlines indicates “this command continues on the next line”, but Windows doesn’t seem to recognize it as such.
Instead of using command line, you usually make HTTP calls in the programming language of your choice. Curl commands are just a clean way to represent those example calls.
i made a new try. installed the openSsl win64, reinstall curl.
Manualy created all certificates following the shell.
Return to hello world project.
replace all simple cotes on unix comands to double quotes to match windows cmd.
Remade every step, and the result is backend runing but frontend hosted by developer rig has error 404 on browser
From those pictures, you don’t seem to actually be running the dev-rig, you’re just running the backend and frontend of the extension. Have you set all the required environment variables and run yarn start from the rig dir?
You may want to revoke that secret key, you’re not meant to share them publicly and it’s a security risk. Also, as you’re using a different port to that shown in the examples for the extension assets, have you correctly set your extension to the correct URI, as it may be trying to look for assets on 8080, rather than the 8081 that you’re using.
