Who has two declaws and just spent way too much time setting up a personal wiki on a raspberry pi?
If someone told you that setting up a wiki was easy, someone lied.
Like goddamn, I spent 2 hours trying solve a login problem that, from what I can tell, can be caused by approximately 17 different things. My version of the problem was fixed by changing CACHE_ACCEL to CACHE_ANYTHING in localsettings.php. There's like 16 other ways of fixing that problem, and none of them seem to be related to one another. I HAD TO LEARN SQL SHIT! AND NOTHING I LEARNED THERE FIXED ANYTHING! NOT A GODDAMN THING!
I can't even remember why I wanted to set this thing up now. I think I was going to use it for note taking, or something?
I would like to give a huge, huge thanks to whomever cooked up ssh back in the day. No sarcasm, being able to control my pi from a terminal emulator on my laptop turns out to be INSANELY useful!
Also a huge thanks to whomever did the scp command, also hella useful for getting files from the laptop to the pi and vise versa without having to set up ftp servers or shutting down the pi and ripping the msd card out every time.
Like, seriously though, fuck SQL. And it wasn't even the thing causing the problem, it was just that God awful an experience. Well, one of the problems. There was the chmod thing. And the learning curve of Apache on Debian - I learned a little bit about a decade ago on Windows and it tripped me up a little, but that's on me.
And god bless Linux's ability to create aliases. So much repetitive typing saved by that simple ability.
Alias realias="source ~/.bashrc"
Alias restart="sudo systemctl restart apache2"
Alias nanowiki="sudo nano /path/to/LocalSettings.php"
Is it possible to, I dunno, set up a router to translate certain urls into internal ip addresses? Like how some of those wifi extenders can do for accessing their setup server. Like resolve http://something.here into 192.169.x.y instead of hitting up an external DNS server?
