I have done a site using node.js with an sql lite database, Mailer and other nice features. Has their been any new features in Wappler to help with this transfer?
So as far as I can tell from info on the net you
1.) create static page
2.) copy code from .ejs file and save.
that's to simple must be more to it.
Unfortunately, there is no easy path to convert to .asp or .php (php is your best bet for shared hosting). Your best option is to upgrade your hosting.
For hosting a web application with NodeJS, SQLite, and a mail server, you'll need a provider that supports lightweight databases, efficient server-side scripting, and email integration. Here are some tailored recommendations:
Best Hosting Options
Kamatera – Offers flexible cloud hosting with support for NodeJS, SQLite, and mail servers. It's ideal for scalable applications.
Hostinger – Affordable and user-friendly, with SQLite support and email services. Great for small to medium-sized projects.
A2 Hosting – Known for its speed and reliability, it supports NodeJS and SQLite, and has easy email setup.
Webdock – Super affordable VPS hosting with SQLite and mail server capabilities. Perfect for developers on a budget.
DigitalOcean – Provides cloud hosting with NodeJS and SQLite support, and integrates well with third-party email services.
Pricing Highlights
Webdock starts at AU$0.95/month, making it the most budget-friendly option.
Hostinger begins at AU$5.99/month, offering a balance of affordability and features.
Kamatera starts at AU$4.00/month, with customizable plans for scalability.
As @brad said.. no easy way.. so save you loads op headaches.. i would recommend going with php in the future. If you not going to use "realtime" data with sockets.. and some schedulers.. then no point in doing nodejs... in my opinion... not worth all the setup and configurations ... php is simple out of the box and works on any shared server and cheap as dirt...
Yes node is cool... im not saying its bad.... but the amount of things you have to do to get this going and what it can do extra.. well not worth it for me.
So my recommendation is.. go with php in the future.. works on 99% of shared hosting... easy to setup... just waiting now for the node guys to jump on me
Hello Ben
Thanks for the input, I am checking with the ones you named.
One strange question, Why does Wappler push NodeJs, when it is such a pain for the developers in the states to get up and running? also you are selling a real nice developer platform why not work with someone here in the states to make it easy to host?
J
There are plenty of hosts in US (and Canada) that support Node. Even GoDaddy. It just costs more. It's not a fault of Wappler how hosts set up and cost their hosting.
I personally won't use node due to it's complexity and hosting costs. But having said that there are features such as websockets that is not supported by PHP. So Node is a very powerful pathway for larger/complex projects. Node is very powerful but is really best suited to experienced developers.
Note: Just did some research and it looks like GoDaddy actually may support Node.js. It just needs to be set up in your cPanel. Contact their support and they may be able to help you.
Research: GoDaddy's Node.js hosting options are integrated within their general web hosting plans, which start at around $4.99 per month.
I use a CapRover droplet on Digital Ocean. CapRover handles all of the aspects (nginx, docker, multi-site hosting) of my old shared hosting on Hostgator.
I have a number of small community sites and staging site that I'm able to host on one server to a commerical/production Nodejs sites. Instead of FTP, I able to pull production code from Github. I enjoy that it forces a backup of my code.
I had a problem a while back and the developer was able to fix something that was unique and even pushed an update within days. Support is always important.
Wappler dont push it, node was introduced by popular request from users.
It's not a pain to set up, just different.
It is a so much better platform, easier to develop.on, faster, more features and can give the user a better experience
Yes, it may cost a few dollars a month extra for hosting but well worth it.
Personally i use a VPS and ftp (works out under $2 per month per site) but many favour cloud providers such as Digital Ocean and docker deployment at $5 per month for a droplet ). Docker makes it simple if you dont want to configure a vps (instruction to do that on forum as well as vps setup)
Most of the NodeJS web apps I've developed are deployed via Docker on Ubuntu VPS, typically starting at USD6.00/month for 1CPU, 1GB RAM setup. If an app requires more resources, I upgrade to 2CPU, 2GB RAM or higher configuration servers, allowing multiple replicas to run for more efficient performance.
Even though the monthly cost for the smallest VPS may be higher than shared hosting, the time savings and ease of deployments via Docker make it well worth the additional expenses.
If you need to run / deploy multiple NodeJS project (for testing or development purposes) on a single VPS, that is also entirely possible, further reducing the cost.
Wappler offers excellent built-in support for setting up remote servers and deploying projects via Docker in Resources Manager. NodeJS might sound daunting initially, but once you experience the ease of deployments via Resources Manager, you wouldn't want to go back to other deployment methods.
I'd like to add that Wappler allows you to select which server type you want to use for your Project and does not 'push' any one of them upon the User. The choice is yours and is not defined by Wappler itself.
Yes, you can use your GoDaddy domain with Railway.app! You'll need to update your domain's DNS settings to point to Railway's servers. Here’s a general overview of what you’ll need to do:
Get Your Railway Domain Settings – In Railway.app, check the settings for your project to find the required DNS records.
Access Your GoDaddy DNS Settings – Log into GoDaddy, navigate to your domain settings, and find the DNS management section.
Update Your DNS Records – Add or modify the necessary A or CNAME records to match Railway's requirements.
Wait for Propagation – DNS changes can take some time to update, usually within a few hours but sometimes up to 48 hours.
Railway’s documentation should have the exact records you need, so it's worth checking their official guide to make sure everything is set up correctly.