Node.js applications hosting

Started by inaevrodom, Aug 28, 2022, 01:54 AM

Previous topic - Next topic

inaevrodomTopic starter

Please tell me about hosting for applications written in Node.js.

And here's what I don't understand.
With web applications in php, everything is clear - I registered an account at hosting provider, created a directory + attached a domain to it, uploaded files via FTP or via PU, created a database and voila - work.

Is it possible to do the same with Node.js? If yes, what hosting providers allow it? First of all, they are interested in free ones or with a trial period of more than 2 weeks (they are not interested with moneyback). I want to look at a couple of Node.js engines from the inside.

Yesterday I killed almost the whole day to deal with hosting providers with Node.js. After looking at a few - everyone is the same: I need to download and install 3 applications (I'm under Windows) - for Node.js, for Git and for the hosting itself. (Particularly for heroku).
At the same time, deploy from com. lines. It's some kind of nightmare.

How to fill in archives and expand - this is not written in the mana, but there was not enough strength to google. Also, you have to deal with the base.
There are no control panels, not even FTP
generally, I don't understand - are these features of the technology, and all of them, or are there such that you can work like with regular php applications?
Is it necessary to install applications from Node.js and Git on the desktop and "work" (rather pervert, not work) from the command line? Without this, why not upload files to the hosting?


Theoretically yes. But no one will do this.
Just like no one uses bash for web scripting. Node/python/ruby/etc applications listen on a port/socket, and puff was deliberately deprived of that ability from the start. It has been added to php7. Since most monkeys easily pick up WAMP and can read "php for monkeys in 3 days", enterprising people gave them the opportunity to rivet websites and place them on their hardware.
The service is called hosting. All these pythons with nodes of yours are a relatively newfangled phenomenon and some people even file their hosting providers for all sorts of Django or RoR. But the architecture of applications in these languages remains the same -- the application listens on a port/socket/pipe and responds. For that reason, no one will separately administer two and a half python/node scripting services for Tom or Smith.


You misunderstand something. What is the practice in php: Apache / megawebserver listens on the port, parses the URL and sends it to the root directory .../www/slicksite/ for processing, where php scripts are located that process the data and return the response back to Apache, which gives the answer to the client.
In the case of a node and a company, you yourself listen to the port and by and large you don't need any Apache, but on the "hosting" it is already there and configured and no one will open separate ports for each client because this is a load on the operating system. it is not necessary to produce select/epoll's as flies. You remembered this when you administrated the lamps, but then you heard about the node and forgot everything, yes. Therefore, you will not be able to work with the node "as with php" and the application on the node is not "the same as in php, only in JavaScript". It is necessary to write in PHP as in PHP, but if not, deploy it taking into account the peculiarities of the node, along with the pain from the lack of rdp.


The node is deployed in the same way as you run it on your machine. Rent a virtual machine (VPS \ VDS) and deploy everything there. You can even take a virtual machine on Windows. There is generally an RDP connection with the same desktop as on your machine. With support for copying by Ctrl+C, Ctrl+V.