For files uploaded to cloud drives, it'd be very useful if it was possible to run them via special URLs like https://repl.endbasic.dev/username/file.bas. The idea here would be to open the interpreter, tell it to load the file, and then execute it.
There are two open questions here.
The first is what to do with public files. Such files should be probably visible and executable by anyone, maybe even those without a service account. That poses problems on the service side though, because it currently requires authentication for all requests.
The second is how to perform authentication if we choose to need it for all files, or if it is needed to access a non-publicly shared file. Right now authentication happens within the client context and is not visible from the browser (i.e. there are no cookies involved), so we'd have to introduce a login prompt somehow.
Maybe the easiest answer is to always require authentication and make the auto-execution process be: open the interpreter, ask for a username/password, load the file, and execute it. Which seems reasonable for the first file you load, but might get old if you try multiple and have to log in every time. That said, maybe this is sufficient for now given the small user base...
For files uploaded to cloud drives, it'd be very useful if it was possible to run them via special URLs like
https://repl.endbasic.dev/username/file.bas. The idea here would be to open the interpreter, tell it to load the file, and then execute it.There are two open questions here.
The first is what to do with public files. Such files should be probably visible and executable by anyone, maybe even those without a service account. That poses problems on the service side though, because it currently requires authentication for all requests.
The second is how to perform authentication if we choose to need it for all files, or if it is needed to access a non-publicly shared file. Right now authentication happens within the client context and is not visible from the browser (i.e. there are no cookies involved), so we'd have to introduce a login prompt somehow.
Maybe the easiest answer is to always require authentication and make the auto-execution process be: open the interpreter, ask for a username/password, load the file, and execute it. Which seems reasonable for the first file you load, but might get old if you try multiple and have to log in every time. That said, maybe this is sufficient for now given the small user base...