I'm going to have another go when I get back to the computer later...like all things, till you've done it once it can be a bit daunting but I'll get it eventually

Reply to this note

Please Login to reply.

Discussion

I've never used name cheap for hosting before but as long as you have a shell you can probably get node running and start hacking at your project. You can probably also do the development locally (I find this to be faster) without having to pay for hosting until you have a working program.

I already had the domain and hosting so I figured I'd build in situ, that way I can check how things appear on various screen types as I go too which I realised I needed to do when building static websites in the past, but just in case I decide to build locally, how much of a ball ache is it to transfer what you've done on your own machine to your hosting provider? Is it a quick simple process, or something else to learn and get my head around? 😆

If you keep your code in git it's pretty easy to clone it anywhere. Also generally advisable as a way to track your project history and avoid breaking things or ending up with different versions floating around.

I have to get passed my nerves and use git, I'm just a bit coy given I've not done any coding in 26 years till I started on Python last year