Simple seed react/express deploys to Azure app service

I need someone to set me up with a seed repo. I'm a bit over-committed and don't have time to read all the documentation needed at this moment. It should be pretty straight-forward for someone who already has the requisite skills. I'd like a demo app that I can just start hacking at with the major bits wired up, but no meaningful content yet. Client tech: react, react-router 4.x, redux. Here's a repo that would work fine: [login to view URL], and is maybe preferred. SCSS (or Compass) integration should be added. Server tech: Koa or express api and serving the client. I followed this tutorial and understand it, so just using it as the base is great: [login to view URL] but you could also use something else similar. Deployment: azure app service. I already understand how to set up continuous deployment through git, and that's what I'd like to use. So, the deliverable is a repo I can clone (or unzip, or whatever) that: 1. Works in linux (including an Azure linux app service, not IIS). I'm using vim, not Visual Studio. 2. I can run npm start and get a dev server to some blank-ish react/router app that integrates SCSS and has a .scss file to get me started. 3. Serves the react app from static, and handles api calls through koa/express. 1. It only needs a "hello-world" api call, and some UI button to confirm that routing to the api works when deployed on Azure. 2. it should have at least two routes so I can confirm that when I deploy it to azure, routing is handled correctly when deployed on Azure. 4. A build step like npm run build or similar to bundle everything into, say, ./build (or some other appropriate name). babeljs is a little preferred, maybe, but webpack or something else is fine. 5. When I commit to master, there's a correct [login to view URL] and [login to view URL] file (and whatever else is needed), so my Azure App Service pulls the newest commit and deploys. It must handle client side react-router routes when deployed on Azure. I think someone may already have such a seed/starter, or be able to make one in an hour or so. The part I'm having the hardest time with is Azure, and I don't have time to read docs in minute detail. This is just a way for me to temporarily skip the plumbing I don't know and make progress on the app itself. Thanks