3 ms·
However, presumably you wanted to test locally before deploying, so you needed a local install. Tools like XAMPP to simplify this were as relatively bloated as
by Macha 5y ago
However, presumably you wanted to test locally before deploying, so you needed a local install. Tools like XAMPP to simplify this were as relatively bloated as the modern create-react-app or whatever.
And then you find the software doesn't work because it relied on imagemagick to resize avatars to display the index page and your web host skimped out on the imagemagick module in their PHP deployment to minify resource use or it was just too much effort for them to deploy because it was the 2000s and they were using Slackware on their production servers.
Oh and the web host disabled .htaccess support so you need to turn off the pretty URL support in the config files. Oh and their default config (which you can't override - see .htaccess) is insecure as it means people can execute PHP files from the upload directory. So then you got owned because of that.
Oh and the MySQL configuration or old version used had some weird ideas about character encoding, so good luck with those € signs.
And then you wanted to install a plugin for phpbb or something and the instructions were basically a diff in textual form on a forum post.
- nicoburns 5y ago> However, presumably you wanted to test locally before deploying, so you needed a local install I wouldn't necessarily presume that. I mean I would want that now. But for my first forays into web development, I didn't have that. Precisely because it was hard to setup. I would just FTP stuff onto the "live" server (it wasn't exactly a critical site anyway, so if it broke for a while then that didn't matter so much). There were editors which could edit files directly on an FTP which made the dev workflow pretty seamless. Stuff like imagemagick could indeed be a pain. But you could at least get started without that. In general there were lots of problems, but the on-ramp to some dynamic behaviour was really minimal.
- cesarb 5y ago> However, presumably you wanted to test locally before deploying, so you needed a local install. Or you did it like mentioned on another comment here (https://news.ycombinator.com/item?id=31247426 https://news.ycombinator.com/item?id=31247426): "copying homepage.php to homepagenew.php, hacking on it until it works, and then renaming homepagenew.php to homepage.php".
- 6510 5y agoThe old homepage.php is renamed homepage-2022-03-05.php and either left there indefinitely or deleted after the next backup. You may even have a script gathering urls for .php files starting with "homepage-" and echo a link for each chronologically (sorted alphabetically) No need to self host a git server.