I'm wondering what setup you guys use to develop brightscript (or node for that matter). Currently i'm either writing my files to an USB and plugging that in, rebooting the device. Or i use the web interface to upload new codefiles and a terminal session to execute them again.
Neither are very convenient, is there some better way? Ideally i'd push the file on save from VSCode, but i cant find a way to enable FTP on the brightsign.
As far as I am aware, FTP is not available on Brightsigns.
Developing in VSCode, then uploading via the DWS, then stopping and restarting the new code via the terminal is how I do it. It works for me and isn't too much of a problem. It works for both Windows and Mac.
Thanks for the response!
you can use sftp ones you enabled the ssh port
I'm actually having some success uploading files via VSCode itself too. Using this rest client plugin its possible to do a PUT request to `/api/v1/files/sd`.
For developing smaller sections of especially complex code, or when working with Brightscript objects you're not familiar with, nothing beats live-coding directly on device using the debug console. Any day that I'm doing development work on a project, I probably spend an hour live-coding, as it's faster than the alternative edit-upload-restart-debug cycle.
https://docs.brightsign.biz/space/DOC/2171994116/BrightScript+Debugger
Very handy if you have any amount of development involving the roSqliteDatabase and related objects, regular expression work, content management objects, double checking JSON structures, etc. Sometimes I'll just use it to verify variable types are correct when transforming data between objects.
Cheers,
Ken
The best setup for BrightScript dev is using the BrightSign Developer Extensions in VSCode with the BrightSign Plugin for VS Code or BSN.cloud workflows. Since BrightSign doesn’t support FTP, you can use the BrightScript Debugger (telnet) and the BrightAuthor:connected tools to streamline deploying scripts. Look into using BrightScript VSCode extension + brs emulator for local testing, then deploy via BrightAuthor or HTTP POST for quicker updates.
You’re not alone. Working with BrightScript can feel slow when you’re constantly rebooting or uploading through the web UI. The good news is that most developers move away from the USB method once they set up a smoother workflow.
A common approach is using the BrightScript debugger and the BSN tools that let you push files over the network without rebooting each time. If you’re on VSCode, the BrightScript extension can help streamline this. It won’t give you full FTP access, but it lets you run, debug and push updates much faster than manual uploads. Some developers also set up a lightweight local server and point the device to it so changes sync automatically.
It’s not perfect, but once you switch to network-based deployment, the process is much easier than swapping USB drives or restarting the device for every small change.
Can't find what you're looking for?
Contact support