Now if you go deeper and want to run multiple things simultaneously, each accessible via a domain instead of a port, accessible from outside of your home, properly backed up and with a valid HTTPS connection, and then you hear about this thing called Docker. That website usually serves traffic via a webserver on some port, and you access it via local network IP and a port (example: 192.168.1.100:8000). In most simple self-hosting scenarios you just "install a website" on your spare laptop or whatever and you're good to go. So, to decipher that comment above: you usually don't have to worry about how things run automatically because that's usually pre-configured when you install them. If you know your local IP, you can also open it from a phone and download stuff from your desktop, zero apps or cables or FTPs necessary. For the simplest example, if you run `python -m rver` in a terminal on a Unix-like system, congrats, you can now browse your files in a browser (127.0.0.1:8000). Webserver → what allows you to "run websites" on your own machine. It's how you install and update packages (packages could be a fully fledged graphical app or just a terminal command). Package manager → essentially the same as an app store on a phone. Unit files → fairly simple text files that are used to define such stuff for systemd (usually in /etc/systemd/system and /usr/lib/systemd/system). Systemd → does a lot of things on modern Linux systems, amongst which is dealing with services that should autostart (think: both low-level stuff like Bluetooth or user-level stuff like a Dropbox client or a VPN or whatever). If I ever get to a point where my own intuition or knowledge isn't good enough, and I don't see the answer staring me in the face via some comments in the code, or some error code thing, etc, etc. So what am I reading? Well, it's quite simple. Go figure, right?īut still, those books lay unread in a desk next to me as I type this. How do I know what to tinker with? I read, ironically. This is how I make mods for games usually, when I tinker at all. If I want something in a program to do something else, I alter the code and reverse engineer it until it does what I want. Can't be damned to? I taught myself pretty much everything I know through trial and error. ![]() ![]() And that can be hellishly important as a skill.īut the fact remains that I have a A+ book from Comptia left unread that I found at a 2nd hand store, a book on Bash that I found at a bar also unread, and a book on Python from O'reily via Amazon yes, unread. I know enough to know when to not do something, essentially. Sure, I fix computers for people, but that's kinda easy. Yeah, you could say I am even still 'there' to some degree.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |