Well first we need to setup a bunch of folders, and we’ll set it up in a “nice” way for using Version control, some people may prefer to keep a separate repo for their EBS from their frontend for easier deploy. be representative of Hosted test and above.work behind (a real) SSL for testing on the Twitch website (or rig).do some clean up on JS/CSS, both for development and production,.“static” host the HTML, JS and CSS for an extension,. But I’ve normally started it in a terminal as I’m testing on the actual Twitch website. The “rig” that I use is Developer Rig compatible since it is just a node command. Personally at the moment I tend to write my Extensions in pure/vanilla JavaScript without libraries, since in most cases I’m just running a few fetch requests and drawing DOM elements, but the more interesting parts come with my compilation/bundling for hosting. The Developer Rig, will either just “dumb serve” a folder of static files, or you can give it a full command to run, handy for WebPack/React/JS things that people need to pre-compile first.īut the big thing it won’t do is SSL Termination so whilst you can easily test your extension in the Rig, you won’t be able to easily test it on Twitch, which is the purpose of this little Dev Environment. The Hosting options in the Developer rig. One of the useful thing’s it can do for you is “host your files” for you when your extension is in Local test. In Part 4 we wrote about the Twitch Developer Rig and what it can/can’t do. This week we are actually going to write some code! Amazing I know! We’ll be using nodeJS and some basic shell scripting, here just for some simplicity.įirst off apologies for being 3 days late on this entry in the series!
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |