This is exactly where I am now.
I can build a website with Next.js for example but I'm unsure of how to handle it for clients. For example, a client asks me for a personal blog, where do I host it? Should I use CMS so he's the one managing the content? What CMS is user-friendly for simple clients?... I'm lost with this process of where to host what, and at what cost.
Hi, thanks for your comment!
It sounds like a managed hosting plan would be good for your case - there's lots of companies offering this so search around for a good price. You could host it yourself or do unmanaged but it's a lot more work to learn how to do that.
I'm a fan of using WordPress for simple blogs as that's what it was originally made for. You can use the WP REST API to feed data to Next.js.
To have the front and backend on the same server you'll want to be able to create subdomains with your hosting provider so you'll need to make sure they can do that. Usually you'll be paying ~£5 a month, but if you have an unmanaged hosting plan (basically just a terminal and FTP) you can host as many websites and domains as it can handle. You probably won't need a powerful server for a few websites so the cheapest option is usually fine.
That's not much detail, but I hope it points you in the right direction! Good luck 😸
Since in the article you mention "managing your won server" as a step to progress from a beginner to intermediate developer, I'm very interested in that solution. Currently, I'm building a blog for a friend who is a researcher and an online portfolio for a friend who is an artist. I was thinking of hosting both of them on the same server, and creating for each some sort of back-office where they can manage their content.
Could I set up this in Docker for example?
thanks for your last reply, I feel like it gave me a direction.
You might be able to do that in docker, I'm not actually sure - the way I'm doing it on a project I'm working on is using nginx to create subdomains. If you just Google 'multiple subdomains with nginx' you should find something. Essentially you'll just have different folders for different websites so you can add your friends' domains for the frontend and then subdomains for the backends, e.g. api.your-website.com
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is exactly where I am now.
I can build a website with Next.js for example but I'm unsure of how to handle it for clients. For example, a client asks me for a personal blog, where do I host it? Should I use CMS so he's the one managing the content? What CMS is user-friendly for simple clients?... I'm lost with this process of where to host what, and at what cost.
Hi, thanks for your comment!
It sounds like a managed hosting plan would be good for your case - there's lots of companies offering this so search around for a good price. You could host it yourself or do unmanaged but it's a lot more work to learn how to do that.
I'm a fan of using WordPress for simple blogs as that's what it was originally made for. You can use the WP REST API to feed data to Next.js.
To have the front and backend on the same server you'll want to be able to create subdomains with your hosting provider so you'll need to make sure they can do that. Usually you'll be paying ~£5 a month, but if you have an unmanaged hosting plan (basically just a terminal and FTP) you can host as many websites and domains as it can handle. You probably won't need a powerful server for a few websites so the cheapest option is usually fine.
That's not much detail, but I hope it points you in the right direction! Good luck 😸
Since in the article you mention "managing your won server" as a step to progress from a beginner to intermediate developer, I'm very interested in that solution. Currently, I'm building a blog for a friend who is a researcher and an online portfolio for a friend who is an artist. I was thinking of hosting both of them on the same server, and creating for each some sort of back-office where they can manage their content.
Could I set up this in Docker for example?
thanks for your last reply, I feel like it gave me a direction.
You might be able to do that in docker, I'm not actually sure - the way I'm doing it on a project I'm working on is using nginx to create subdomains. If you just Google 'multiple subdomains with nginx' you should find something. Essentially you'll just have different folders for different websites so you can add your friends' domains for the frontend and then subdomains for the backends, e.g. api.your-website.com