Setup guidance needed please - using my own server/MSSQL (not local)

Wappler General Need Help
1

I really need to get moving forward but need to understand the setup first. Want to use Node, not PHP

I have my own Windows 2018 server and MSSQL instance. Already use node on that server too.

  1. Do I need any “docker” stuff running on my Mac?

  2. I have created a database connection to my server (and thus I know how to point to a dev db vs. production). But this was through local installed Docker from Ken’s tutorial. Does Wappler update my Node files/routes/etc. on my server (for Production) for me or do I do the node part locally (for development) and copy the node files manually to my server? Very confused on setup.

1 Like
2

Hi.
Wappler has a built in NodeJS server. So you don’t need Docker at all.
You dev setup would look something like a target with Local deployment, and DB in Globals pointing to your MSSQL instance.

This should get you going on the local machine and allow you to test the app on localhost:3000.

As for production, you need to explain a bit on how your production server is setup. Or do you even have a production server at the moment?

3

Docker is optional, it will allow you to setup a local dev server and database. For NodeJS you can use the buildin/local server and no docker is required.

There are a lot of ways to deploy your project to the server, in your case I assume that it will probably be using FTP or file copy when it is in your network.

I don’t know the exact setup of your server, but normally NodeJS runs itself as a server and you then use IIS in front as a reverse proxy. The NodeJS server will run locally exact the same as on the remote with the same routes, you will only need to configure your server to forward the traffic to the NodeJS server.

4

I have a Windows 2018 hosted server I control 100%.
DOES NOT use IIS. Tomcat & MSSQL & node.

In previous models, Appgyver would get data from my endpoints. And then Bubble. Now, with those removed, I imagine my node server is public facing?

I connect to my server via RDP. I'd rather not FTP to it - zipping my files and then a copy/paste into a folder on the server, then unzip is really fast.

5

Do you access the Tomcat and Node server on different ports?

The Node server with Wappler doesn’t support https, it is normally used after a reverse proxy like an nginx server which then handles the static files and takes care of the secure https connection. If you don’t need that extra security layer then you can make your node server public visible. It is possible to enable https with the node server, but that will require some code changes and you need to supply some certificate keys for it.

6

yes, i had been. 80/443 for the main server.
and another for node for incoming API.
and another for MSSQL for local access and external tools.

I use SSL in node, so thats no bother.
I don't mind setting up nginx, just have not. how much monthly cost is there for a server to handle just that?

7

So to run on production you will have to copy paste the files and restart node server after pasting.
Or, you can setup FTP to automatically upload files as you save them.

As for the rest of the server config, its not something I understand very well.
I use either Wappler Docker deployment or Git based Caprover deployment on Digital Ocean Droplets.