It's a webserver. Damn.
Discussion
i don't think so. i mean not to say it doesn't include one. i have been working with a "bun" based app in my new job. but "webserver" is an extremely small thing. literally any language with a HTTP library can fling files based on a router that essentially works a bit like a filesystem, except with what are kinda like little sub-apps that take parameters. and even then, the line is blurry because PWAs also process those parameters but the whole code is already there in the browser to change the view instantly.
haha, man, today doing the router dance to find all the places the stupid code needed the identical information over and over again, must have been like 10 elements scattered across two files before the damn thing gave me a new route. idk why javascript developers don't like having all related things in one place. they made JSX and TSX file format for this purpose and then i come back 10 years later and it's back in a dozen pieces again.
make components componenty again
er, i misread what it was.
though maybe the webserver can run the app since it is a javascript thingy. probably not, idk, might be some voodoo you can do with it to bundle it up, like the old days with webpack.
It's react and node.js.
I sent the provider an e-mail, that we need to change.
so it only works *as* a webserver not *in* one :)
who even makes web apps that aren't themselves webservers anymore anyway?
Everything is a node.js app. I weep.
i'm working with react at my paid gig at the moment. i weep at the objects and the nonatuplicate copying of the same info in several different places, the utter disregard for any kind of simple, readable syntax, and waiting 10 minutes for the IDE to finally index all the symbols in the source code.
if this was Go there would be no duplication, the indexing would take 10 seconds and there would be no such thing as "something went wrong". and it wouldn't be stupid error codes like C, it would be informative strings. potentially they could even have source locations.
javascript ninjas have no idea how dangerous their language system is. but then, nobody seems to care, and tehy build KYC systems with it and then wonder how it all ends up on the dark web a year later.
They support node.js on the webserver. But I also prefer containerization, for the DevOps.
They also support git integrations and triggering. So they can run nodejs builds from a git mirror, so that might be an option.
I'm canceling it, probably. A server that can't handle containers is completely retarded.
Lol it's shared hosting. Quite popular and affordable solution :) Mostly made for LAMP stacks because the resources can be shared. The infra is much easier and cheaper to design compared. Same reason I offer static site hosting but not container deployments unless I write or fork them for my customers.