When deploying our projects, we specify our entrypoint, and we don’t have much room after that. It would be beneficial to be able to run different scripts on the same project for various purposes.
Example 1: Isolated crons that don't slow our imports when they are huge. (And without having to dynamically import them)
Example 2: Migrations scripts on our KV database directly on Deno Deploy. This would allow to not require an access token that we use on our local machine to run the script.
Describe the solution you'd like
I envision a file browser that allow to open your file in the same view as the Deno Deploy Playground. Then you could execute the scripts directly, enabling isolated cron jobs from the entrypoint, and facilitating direct execution of migration scripts on Deno Deploy.
Ideally, you would only see the content of the script, and the console. Therefore, you wouldn't need the playground's integrated browser: #566
Describe alternatives you've considered
It could also be nice to just be able to specify an entrypoint file, or a whole folder, for our crons on one hand, and our migrations scripts on the other hand, that are isolated from our app entrypoint.
What problem are you trying to solve?
When deploying our projects, we specify our entrypoint, and we don’t have much room after that. It would be beneficial to be able to run different scripts on the same project for various purposes.
Example 1: Isolated crons that don't slow our imports when they are huge. (And without having to dynamically import them)
Example 2: Migrations scripts on our KV database directly on Deno Deploy. This would allow to not require an access token that we use on our local machine to run the script.
Describe the solution you'd like
I envision a file browser that allow to open your file in the same view as the Deno Deploy Playground. Then you could execute the scripts directly, enabling isolated cron jobs from the entrypoint, and facilitating direct execution of migration scripts on Deno Deploy. Ideally, you would only see the content of the script, and the console. Therefore, you wouldn't need the playground's integrated browser: #566
Describe alternatives you've considered
It could also be nice to just be able to specify an entrypoint file, or a whole folder, for our crons on one hand, and our migrations scripts on the other hand, that are isolated from our app entrypoint.