My security concern was for the connection between the hosted platform and the local data.
If you do it all at home, then that is no longer an issue.
Note also that yo can host static content with your own custom domain on github pages or cloudflare pages and they'll sort out the https for you, you would then just need to maintain the backend (if it's an API). If you're using server side rendering for your html that's a bit more involved but there are probably still free ways to achieve that.
You can generally get cheap linux based vm for about $3.50 USD per month (AWS lightsail) if you need to do something with processing and a database etc.
Sorry I am late here but I can help
well I am a student too but I am hosting my website and testing it as a hobby only
btw, straight to the point for hosting, I used many free hosting providers but I didn't like any cause of some limitations or other causes now I am using Azure free tier ( free for 12 months ) to host my website on Azure VM, if you want I can help you to get Free VM for hosting and Free TSL/SSL with Let'sEncrypt it's just too easy believe me
interesting, I didn't know that. Where can I get more info about this? I need to put my react somewhere, but also django, I believe react is static content? I am not sure. Django probably not as it manages a database.
Sure. What technologies are you using? I am working with react frontend and django backend, currently looking for a place to put django, though I am thinking about hosting it at home. So I would need to make it work with django on some local machine. Currently looking into certbot, which unfortunately does not permit me to get a certificate for an ip or localhost (which I guess makes sense).
I am still learning a lot and I just want to mess around, the only reason why I am trying to get a certificate is because my react code apperently won't set a cookie if it is not coming from an https, even though both servers are running on localhost...
It can be static (just html and javascript loaded into the browser) or server side rendered e.g. node js is on the server to pre-process requests dynamically so that the HTML for your page is "hydrated" after initial load to inject the additional components it needs to be dynamic.
Django is server side python and runs on your server and is indeed dynamic.(needs a server you control).
Well, I got my react running on firebase which also (I believe) only supports static content, so should also work on github.
Can't you "test" with a self-signed cert that you "trust"?
[until you get it all figured out and then swap it for a real cert]
If I can then I don't know how, I am very new to webdev, especially when it comes to protocols and networking.
@Plegeus I recently got a VPS for 90 cent (euro) per month. 1 vCPU, 1 GB RAM, 10 GB SSD. Scaleway calls it stardust, and it has pretty limited availability -- it's IPv6 only, of course. You can save a lot of money if you don't need IPv4.
I guess if you stick Cloudflare (free) in front of that you also get their IPv4 for free (and their free caching/firewall).
Yup, that's what I am using
VMs are all the same you get the whole server control and install anything just like your local computer/server
I just want to know how long are you gonna host your website Also you want it to be running 24 or 24/7 hours
So why does it matter having both ipv4 and ipv6? Isn't ipv6 the 'new better thing'? Or do I need both to support older machines?
Well I guess that could work, I don't expect a large user base
So it really depends, I am just testing something out, the goal is to have the site available 24/7 to all users, but depending on how successful it is (or isn't) I will keep it running or shut it down. I am mostly looking to get something experience in. It would be nice if I can make some money out of it with google ads or something...
plz check your DM
I did manage to get a local certificate, so I can now connect to the server over https and the browser does not complain. I was having issues with cookies not being set on the client which is also fixed (though I'll probably still need a solid solution when in production so I will look at all the possibilities you guys are suggesting).
There are also several providers that sell OpenVZ VPSs (which are not recommended if you're starting out or want to change/upgrade the kernel -- they are somewhere in between proper virtualization and a docker container) for a few dollars a year.
It's not just "older machines" that use IPv4.
- Some ISPs don't provide IPv6.
- Some home type routers don't support IPv6.
- Some people don't even understand IPv6 [so they don't bother turning it on].
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.