Station data folders

Set the station folder uploaded by RadioBOSS WebSync. Enter one own folder per Website station — for example /radio-data/radio-albena — containing public, private, admin and optional live JSON folders.

This is a Website setting only. It does not create folders, change WebSync, change SFTP settings, read private contents or publish any data. The path must be local to this web server, for example an absolute server path or a path relative to this application.

The public-library import reads only public/songs.json, artists.json, genres.json and info.json for the selected station. It writes the resulting catalogue into this Website database only; it never reads private, changes the scheduler or writes back to SongSync/WebSync.

A current info.json timestamp stays strict ISO-8601 with a timezone. For existing local exports only, a legacy YYYY-MM-DD HH:MM:SS or YYYY-MM-DDTHH:MM:SS value is interpreted in that Website station’s configured timezone; the source JSON is never changed.

The separate schedule import reads exactly admin/schedule.json for the selected station. It reads neither Admin.sdl, admin/status.json nor anything under private, and it never changes WebSync, RadioBOSS, the scheduler, SFTP or the source JSON. A successful manual import is authoritative for its one declared week: the Website marks any older stored Website-calendar starts that overlap that same station/week inactive when they are not in that exact source snapshot. It also keeps a stripped, command-free copy of the same scheduler rules for the Website’s read-only four-week planning forecast. Other weeks and stations are unchanged. Imported folder occurrences stay in the admin calendar only; the existing public programme is not changed by this step.