Quote from: viviridian on Apr 13, 2025, 09:23 AMOpen question: what's the most efficient way to iterate on the packages? I assume you aren't rebuilding the packages and uploading them through the admin panel each time (...?)

Typically I only take that route if I'm doing something with install hooks. Modifying the F9 theme is easiest since everything in the folder takes effect by default, but if you need to add a new hook or are modifying on-install behavior, it needs to be reinstalled. I've considered modifying the database directly (it's not that bad for (un)installing hooks), but the uninstall/reinstall method was easiest for the time being.

Typically what I'll do is SSH into my sandbox server and modify the files directly in the locations they got installed to, and then scp them back when I'm done.

As I write this out, I think for a Docker container it wouldn't be too hard to write a wrapper script that handles reuploading the package to the container, so long as the manifest doesn't change much. It could also help with the initial setup. I'd have to play with the idea when I have a chance to know if it has any chance of working, though.

i could have used some more fully-featured container someone else already built (such as https://github.com/8ctopus/php-sandbox) but that wouldn't satisfy my drive to do things the hard way

I got a basic LAMP setup running in rootless podman. Any method of getting a LAMP stack is viable, a nice quality of that approach is that it is both contained & doesn't require fiddling with permissions if you want to poke smf's files.

1. Set up some kind of webserver with php and a database (e.g. the above thing)
2. Download SMF and unpack it somewhere in the webserver. Navigate to it in your browser and go through setup. (see instructions in my repo for more detail)
3. Clone the f9 repo.
4. Run make. The `out` dir should now contain packages.
5. In SMF go to the admin panel, and then to Package Manager > Add Packages
6. Upload each package except for the theme. Install each of them.
7. In the admin panel go to Configuration > Themes and Layout > Manage and Install
8. Under 'Install a New Theme', upload the theme's zip to install it. IMPORTANT: DO NOT SWITCH THE FORUM'S DEFAULT THEME YET.
9. Go to 'Theme Settings', and click the gear icon for 'f9_theme'. (If you did switch to the new theme, you'll have to switch back. or view source and get the hyperlink for the gear icon, which will be missing )
10. Update both "This theme's URL" and "This theme's images URL" to both refer to `f9_theme` instead of `default`.
11. Also change the default smiley set for the theme to F9.
12. Now change the forum default them to f9_theme.

Open question: what's the most efficient way to iterate on the packages? I assume you aren't rebuilding the packages and uploading them through the admin panel each time (...?)

other than that it's been mostly pretty good. if i want to play a game using the gpu i have to start it with these environment variables
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia

i ended up just installing lutris so i wouldn't have as much stuff to juggle

We have the [code] tag, but that's specifically a block element. Would be nice to have an inline code snippet element ([c] maybe?)

I've been thinking about building an F9 game server (OpenRCT? Lua-based MUD? Quake? who knows) and would like to keep it limited to those who are here, even if the thread itself is publicly visible. This is already doable with attachments, where those who don't have the "view attachments" permission just see "You aren't allowed to view this attachment" where the attachment would be.

The idea would be just being able to write "The password is [secret]haggis[/secret]" and have the word "haggis" be hidden to logged-out users.

wh-
o.o

Quote from: viviridian on Apr 11, 2025, 12:04 AMI wonder whether this is something that packages can fiddle with, or if it'll require directly modifying smf. Not sure if there have been any modifications to this smf or if it's vanilla with packages on top

Any modifications other than the "lightbox" patch are in the F9 repo. Or rather, should be. (If you find any inconsistencies, please let me know, because that's not intentional!)

They all "compile" to the SMF mod .tar.gz archives, and then can be installed through the admin panel.

As for the email templates, they can be modified per-theme, specifically in Themes/$theme/languages/EmailTemplates.english.php (a github link to the default, for reference).

Quote from: viviridian on Apr 11, 2025, 12:04 AMI also don't know if there are limits on packages. back when I was doing stuff with smf I just edited php in prod

That depends. If you're working with hooks, you're stuck with wherever the SMF devs decided to stick a call_integration_hook call, but at least it'll survive minor updates. There's a way to patch files via XML, but... at that point I'd rather just use patchsets.

I don't even *really* know what it does lol.

I've wanted to do that for a bit, just have lacked the motivation to write the docs. If you do end up doing this, let me know if there's any extra info you need!

Security config aside, it's a pretty standard nginx/mariadb/php-fpm setup. I need to get that one "attach lightbox" patch converted to a proper SMF mod, which I'll get to... eventually.