Orchard1.3 installed on Azure. Have built from source
How do I get a nice download link (which doesn't work, but from googling I think should work on single hosted machine) like:
http://www.davemateer.com/media/Default/CodeCamp2012/CodeCampPresentation.zip
instead of this one (which does work)
https://mateerstorage3.blob.core.windows.net/media/Default/CodeCamp2012/CodeCampPresentation.zip
Cheers
Dave
Write a module that exposes its own routes, and proxy the contents through there. It's going to have horrendous performance but it will work.
Related
I have NextJS app with SSG. This functionality was added recently and according to it I should do next-export after next-build to get static files. But after appearing in 9.4 of Incremental Static Regeneration I need to keep server on by npm-start command (in my case I use custom server file with next-express functionality). It works good locally and It works good when I get artifact from Azure. But It doesn't work globally when it will be deployed finally. Help please
Through my attempts, I found that it is impossible to install globally or use next in Azure Web App. That is, it cannot be deployed through Github.Deploying using other methods such as FTP cannot run successfully. It should be related to the azure node environment.
But the method provided in this post says that it can be processed by adding web.config. I think it should be useful and helpful to you. Please read it carefully and try it.
You also can read this document, maybe it useful to you.
I have created a virtual machine on Compute Engine of Google Cloud and I want to host my project made in Node and Angular on that virtual machine. I installed Node on the server and cloned my project from Git, its working perfectly.
My question is, how do I bring that project in the browser?
You should: npm run build. After that you could find dist folder with your project and copy content of this folder to any static web server (GitHub pages and etc)
Additional info
As Rajesh said in a previous answer, your question is a bit ambiguous. I think that maybe what you are asking is for a way to allow http/https traffic to your Google Compute Engine instance. Please feel free to correct me if I’m wrong.
If my assumption is correct, you need two things here. The first one is a public IP for your instance and the second is create firewall rules to allow this kind of traffic from internet to your instance.
We're using Nodejs + Express to create a RESTful web service. During testing we kicked off the service via the command-line, i.e., node mim.js and and tested the service using http://server:9999/mim/GetEmployeeData and that works fine.
The node application lives in inetpub\wwroot\myapps\mim and we want to be able to access it like so:
http://apps.mydomain.com/mim/GetEmployeeData
We're not quite sure how to get this to work with IIS, however. Looking for some help with respect to this.
Thanks in advance!
See this Hosting node.js applications in IIS on Windows tutorial:
https://github.com/tjanczuk/iisnode
It explains many different scenarios and since you din't post a lot of details it's hard to give you a more detailed answer other than pointing you to a good documentation about the thing that you're trying to do.
I updated my open source forum app to ASP.NET Core 1.1, and after battling deployment weirdness (it broke for reasons I don't totally understand, but believe it has something to do with the changing tooling), now I find that routing is broken. When I say it's broken, I mean it continues display links with tag and HtmlHelpers, but they don't match the "clean" routing that they used to. They work correctly locally, but not in an Azure app service.
For example, the correct URL should be:
https://popforumsdev.azurewebsites.net/Forums/first-test-forum
But it's resolving as:
https://popforumsdev.azurewebsites.net/Forums/Forum?urlName=first-test-forum
I get the tooling changing, but this has me totally stumped. Same code, working differently locally and in Azure, and it didn't break until I updated to v1.1. (It doesn't instill a lot of confidence for what I assume will be relatively frequent framework updates, either.)
I don't imagine this has anything to do with it, because it works as expected locally, and it didn't change for v1.1, but here's the routing code:
https://github.com/POPWorldMedia/POPForums/blob/master/src/PopForums.Web/Areas/Forums/Extensions/RouteBuilders.cs
Well, after redeploying twice, this resolved itself. That's even more concerning, that routing would break like that, and that it didn't.
I am coming from Microsoft world so please bear with me on this. I was told I could install node.js and use that as a web server instead of IIS. This is a very small business application. In IIS I can create virtual directory and point to the location of the web page and everything works just fine. Based on very little I read, I have few questions;
Is it possible to run node js as a windows service or any other form so that it runs for ever? I did find the forever package that I think I can use.
In IIS, I can create virtual directory set the port and thats it, I have myself a website.
I do not see any examples where I can use a directory where I have a web page, written in java script and point it to run as a web site. All the examples have some thing like server.js and that runs and routes the call. what is the other way to host web sites and use node.js to simple run as a fast web server.
I was told I could install node.js and use that as a web server instead of IIS.
This is true, but as you already found out then you are in charge of providing for things that IIS was already doing for you (e.g. automatically restart on reboot, or on crashes, hosting multiple sites by creating virtual folders, et cetera.)
You can indeed get all of these things worked out in Node.js and there are several libraries that help on each of these areas. It's not too hard but you'll need to do a bit of researching.
You can also run Node.js behind IIS. Take a look at iisnode http://tomasz.janczuk.org/2011/08/hosting-nodejs-applications-in-iis-on.html
Is it possible to run node js as a windows service or any other form so
that it runs for ever?
The library Forever takes care of restarting the site when it crashes...but I don't know if you can run it as a Windows Service. I haven't tried that.
In IIS, I can create virtual directory set the port and thats it,
I have myself a website.
I assume you are talking about a site that serves static HTML files, right? If that's the case that's very easy to support in Node.js either writing your own web server or using Express.js to serve static files.
I do not see any examples where I can use a directory where I have a web page,
written in java script and point it to run as a web site. All the examples
have some thing like server.js and that runs and routes the call.
Here is an extremely simple example to serve plain HTML files in Node.js https://gist.github.com/2573391 Don't use this in production, though. It's just an example and it does not have any kind of error handling or security.
what is the other way to host web sites and use node.js to simple run
as a fast web server.
As others have said, you should look into Express.js http://expressjs.com/ It provides some of the infrastructure that you are very likely going to need when building traditional web sites.
You say you're running a "very small business application" behind IIS. Unless it's written for Node.js (in JavaScript), it won't work.
There are no examples pointing to a directory and running that as a website, because that's not how things are done in Node.js. You write a Node.js-application and pull in a webserver-library.
Put simply, In Node.js, you don't embed the appliation in the webserver; you embed the webserver in the application.
When I used node.js, I redirected HTTP requests by a proxy server, nginx. I don’t know if you can directly bind node.js as an HTTP server, but for what’s it worth, nginx is pretty nice!
First things first, allow me to share an introduction. IMHO you should take this decision ( of moving from IIS to nodeJS) by adding various parameters. I belong to the Java & PHP community yet I use NodeJS to achieve extremely specific implementation where NodeJS perform the fastest ( fast IO, AJAX-JSON responses & more ). As you are coming with a Microsoft background you should bare with less comfortable solutions.
Yes, its possible to run NodeJs as a windows service and Forever will do fine.
and yes you can create "Virtual Directories" but by creating symbolic links to each of your customer's web site.
I recommend to take a good look at bouncy & express, If you're willing to take this step then these packages is just what you need.
Cheers!