Fix command errors in Nebari server run for templates

[guptaaryan16]

Description

This PR is a follow up PR for the fixes in the code execution while testing in the Nebari server. Particularly we faced two issues, first if we open a template in Nebari, its default folder will be root and if it is the second template opened, then it will try to download and overwrite the previous one. This can be fixed by fixing the nbuid-> nbuid + '-nebari'.

Also we add some extra commands that can help in creating a new directory and store templates files in that specific directory.

Fix #314

Additional context

This issue was discussed in Discord this week.

What is the purpose of this pull request?

• Bug fix
• New feature
• Other

[netlify]

✅ Deploy Preview for code-generator ready!

Name	Link
🔨 Latest commit	c66e3c1
🔍 Latest deploy log	https://app.netlify.com/sites/code-generator/deploys/64feeab6ee1d13000835907e
😎 Deploy Preview	https://deploy-preview-317--code-generator.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[guptaaryan16]

Hey @vfdev-5 seems to work as expected now, can you check on your server as well once?

[vfdev-5]

Is it expected to have this ? How did you test it ?

@guptaaryan16 this does not work!

[guptaaryan16]

Is it expected to have this ? How did you test it ?

@guptaaryan16 this does not work!

Actually for other configurations like text-segmentation, it seems to work, I guess we need to delete some previous notebooks generated for nebari.js like the one you mentioned

[vfdev-5]

Actually for other configurations like text-segmentation, it seems to work, I guess we need to delete some previous notebooks generated for nebari.js like the one you mentioned

It's very annoying that I have to discover during the review. You could have tested the first template at least

[guptaaryan16]

It's very annoying that I have to discover during the review. You could have tested the first template at least

Actually I was testing some solutions for this problem, and it seems like updating nbuid-> nbuid + '-nebari' + <last_commit_hash> may work. Let me test this and then we can merge this PR.

[vfdev-5]

Actually I was testing some solutions for this problem, and it seems like updating nbuid-> nbuid + '-nebari' + <last_commit_hash> may work. Let me test this and then we can merge this PR

Commit suffix is not related to nebari option but have to be considered in general. But in general appending a commit is not a good solution as we would generate new uuid everytime someone pushes to main (even unrelated change).

We may want distinguish cases when the app is run from netlify PR deployement vs from code-generator.pytorch-ignite.ai/ and append commit from PR only, IMO

[guptaaryan16]

Commit suffix is not related to nebari option but have to be considered in general. But in general appending a commit is not a good solution as we would generate new uuid everytime someone pushes to main (even unrelated change).

We may want distinguish cases when the app is run from netlify PR deployement vs from code-generator.pytorch-ignite.ai/ and append commit from PR only, IMO

Let me revert the changes for now and make a second PR for this deployment vs PR build case

[vfdev-5]

LGTM, thanks @guptaaryan16