So, I've been trying to accomplish this for a while. First I posted asking for help getting started, then I posted about trying to open ports on my router. Now, I proudly post about being able to show the world (for the first time ever) my abysmal lack of css and html skills.
I would like to thank everyone in this community, specially to those who took the time to answer my n00b questions. If you'd like to see it, it will be available at: https://kazuchijou.com/
(Beware however, for you might cringe into oblivion and back.)
Since this website is hosted on my desktop computer, there will be some down-time here and then, however I'll leave it on for the next 48 hours (rip electricity bill) only for you guys to see. <3
Now, there are a couple of things that need addressing:
I set it up as a cloudflare tunnel and linked it to my domain. However, I still don't know any docker at all (despite using it for the tunnel), and the process was too incredibly and stupidly easy. I don't think I learned as much as I expected and I didn't feel challenged at all.
The original idea was to do some port forwarding. (This was foolish and a bit of a waste of time). Despite getting a "public-ip-address" from my ISP, I still was unable to open ports successfully. I kept getting the same error again and again. If you'd like to read my original post about port forwarding you may follow this link: "[Solved] ((lie)) Noob stuck on port-forwarding wile trying to host own raw-html website. Pls help".
While I know doing this represents a security risk, I still wanted to at least have a small success with port forwarding. I just wanted to have the raw-internet-connection experience, you know? like, the basics and such. And Cloudflare is holding my hand way too hard, I want to feel like I can shoot myself in the foot (without actually doing so)
But to be honest, I'm quite happy with the outcome. There are many other avenues I'd like to explore in the future, like setting up a reverse proxy with nginx or even darknet hosting (as sugested by another commentor).
I hope to keep learning and some day help another poor soul like myself in a similar situation. I thank you again guys, you're the best.
[TL;DR] This is the best and most helpful community ever! thx <3
Just in case: If your storage is completely full all of a sudden, check
/var/log/nginxif you haven't pointed the logs elsewhere.I know I was pretty confused to find my storage absolutely full, then I found the multi-GB error.log file. When a network interface it was listening on disappeared it filled with errors as such:
(I just reproduced that now on-demand, thus the date.)
There's a tool called
logrotateto take care of logs, but I just did the stupid and lazy thing...Well, in case you get the idea to run NGINX in Termux, and then later you find your phone hot, stuck in a bootloop, it's possible the error.log filled the storage causing Android to crash because it now can't even write system files.
Not that I would have done such thing...
Thanks a bunch!
I will certainly consider this, I had no idea nginx created these log files.
If anything, I can just
rmthem into oblivion right?Sorta. If the log file is open then your rm won't take effect until the application closes the file. You won't see the file anymore but it will still be taking up space. So if nginx is running when you delete the logs you may need to either stop it or restart it depending on how nginx handles this.
Yup.