sudonix

@phenomlab said in Come back PhP, all is forgiven!: I used IONOS for a while, and realised that Hetzner provide a much better deal for those experienced with Linux. I know @cagatay, @DownPW and myself all use Hetzner, and I think @Madchatthew (whom I haven’t seen for a while ) was also considering taking their services. There’s an affiliate link below if you’d like to go down that route Yep hetzner is very very cool and I haven’t seen before a panel magentment as complete as him : backup, snapshot, add cpu core, ram is easy. @phenomlab said in Come back PhP, all is forgiven!: Obtaining a VPS comes with the double-edged sword of being completely on your own with no support, although by using Virtualmin, you’ll find life so much simpler (something I know @DownPW can attest to, as I managed to convert him ) Yep Virtualmin is very cool And it makes life much easier for server management, domain, nginx and so on even if it is always better to know how to do all this in CLI. I would say that the 2 are really complementary

@Panda I have the same opinion here. NextJS is a framework for react, and like angular, I was never one to simply dive off into the deep without having any real need to do so. I’m conversant with nodeJS, vanilla js, and several other languages (including PHP which I have years of experience in and developed / still maintain an application at work that was custom written by me to fulfill an audit requirement), and in all honesty, I don’t really want to spend my life learning new frameworks unless I have a need to do so. I’ve been on the nodeJS train for some time now, and given my adoption of NodeBB, this makes perfect sense. Bleeding edge is fun if you want to experiment and learn, but with so many frameworks popping up all over the place, how many do we actually need? I guess most of this really depends on unique use cases, but I’ve yet to come across an issue that meant I had to rewrite an application in a different language to resolve an issue. It’s almost like using a bulldozer to find a china cup.

@eeeee have a look at the below https://docs.nodebb.org/installing/os/ubuntu/ curl -sL https://deb.nodesource.com/setup_lts.x | sudo -E bash - sudo apt-get install -y nodejs You’ll notice that we are in fact “installing” NodeJS but never actually have a need to reference it. Here’s the nodejs --version command on my dev system [image: 1681584648061-6eb1482e-0c9b-454d-aa84-199bcc845702-image.png] More detail here https://askubuntu.com/questions/1030622/why-do-i-see-different-versions-of-node-and-nodejs

@Sampo2910 said in Updating Node and NPM: Is there a way I can see what the app version of Node is? Then i could install ‘up to that’ and keep an eye out for any changes? Have a look in the source code for the app you are using, or better still, look at the GitHub page which should give you an idea of the version number which is the latest. In the source code you have running, there is typically a README file which should state the version you are running.

@justoverclock Any update ? Thanks EDIT - marking as solved based on the below thread https://sudonix.com/topic/339/digitalocean-step-by-step-guide-to-nginx-configuration