Radio2 was blazing its own trail through static files.
I want it to work with the opmlEditor static file service so they are all managed through one page on the main prefs page. Static file paths will all merge into one page. The users will still be able to save into their own buckets in addition to the sysop-defined buckets.
The changes proved to be remarkably simple.
My server is set up. Probably already running River2, but possibly not.
River2's static folder is set from the Static files page in the OPML Editor. It's not something you can change independently.
Radio2 lets you change the location, and it's not at all tied into the Static files feature. It's not even initialized from it.
The River2 way is the preferred way to go, but we can't undo what's been done in the past. Radio2 must still work the current way, at least for existing installations.
All writes seem to flow through radio2Suite.writeStaticFile.
It might write the file to two places. The sysop-configured location on S3 and the user-configured location.
We could add a third, we could flow the file through opmleditor.writestaticfile, adding a /radio2/ to the beginning of the path.
Continue to respect the pref for the sysop-configured location, but no longer provide a UI for it, and make sure it defaults false.
That way the Static files page configures static file writing for Radio2 as it does for River2.
And we've got prior art for worldoutline.root and any others.
On your Radio2 server, visit the Static files prefs page in the opmlEditor website. Be sure that writing to S3 is enabled, and that you've filled in a correct path and its corresponding URL.
Post something to Radio2. You should see the files show up in the new location as well as the location you specified previously.
That's all you should do. If you were to switch over to use the global static location all your links would break. But if you set up a new server it'll be a little simpler than the server you're running now.
radio2suite.init
radio2suite.writestaticfile
;)
;)
;)
;)