-1

I have planned to separate my application in two layers. One will be the API Rest layer, backed by Ruby and another the frontend, using EmberJS, both in Azure Cloud.

For the API layer, it's fine, we going to use the Azure Web App, which is a container based with Ruby installed.

But for the frontend I'm not sure.

One way is use the Web App based on NodeJS, but, the EmberJS files should be served as static way, so I'm considering to deploy it on Azure Blob Storage, instead.

For deployment it's necessary a NodeJS server? As far as I know we only use NodeJS utilities such as NPM for packet management, but not to serve the application.

Anyone could give me a light on it, please?

3 Answers3

0

The question is a broad ask not suitable for StackOverFlow,

Simple answer would be to use Azure App Services and host both your frontend on nodejs or ASP.NET core and backend ruby as now we support Linux Containers.

Check this blog on how to create your Ruby backend : https://learn.microsoft.com/en-us/azure/app-service/containers/quickstart-ruby

Check this blog on how to create frontend app : https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs

It doesn't matter what you use for EmberJs both Node and ASP.NET core provide excellent support for developing any frontend apps easily. Personally I prefer ASP.NET Core here is the video tutorial to get you started : https://www.youtube.com/watch?v=KAMuo6K7VcE

C B
  • 1,964
  • 14
  • 13
0

All of your application written in .NET, Node.js, Python or PHP that hosted on Azure App Services (Windows platform) is running on Microsoft IIS. Azure App Services can handle these languages correctly because it already has the runtimes installed and has corresponded CGI handler set in the IIS configuration file called web.config. If you don't have any CGI configuration in it then Azure will serve all your application files as static content as well.

So, in this case, you'd need to build the Ember.js App in your local with the command ember build --env production and then put all built files to IIS's virtual directory D:\home\site\wwwroot in Azure.

See also:

Aaron Chen
  • 9,835
  • 1
  • 16
  • 28
0

In the backend I used the WebApp and for the front-end we use Azure Blob, since the EmberJS will host static content, using the https://www.npmjs.com/package/ember-cli-deploy-azure-blob. It worked very well :D, now Azure Blobs is able to configure default documents, such as index.html, pretty same the AWS S3, finally.