Use dope.sh to generate a testable app from production template

[infomiho]

Description

Based on #531

Fixes #524

This PR reuses the existing dope.sh to create a testable app from an app generated by wasp new app -t saas.

The changes are minimal:

• change Dummy to SMTP and use the correct email address
• setup Dotenv Vault

This allows for testing the app in production mode e.g. npx @wasp.sh/wasp-app-runner build.

This PR doesn't setup Stripe, analytics or similar. I think it's not really needed to smoke test the template. We have opensaas.sh with all the bell and whistles for that.

Contributor Checklist

Make sure to do the following steps if they are applicable to your PR:

• Update e2e tests: If you changed the /template/app, then make sure to do any neccessary updates to /template/e2e-tests also.
• Update demo app: If you changed the /template/app, then make sure to do any neccessary updates to /opensaas-sh/app_diff also. Check /opensaas-sh/README.md for details.
• Update docs: If needed, update the /opensaas-sh/blog/src/content/docs.

[cprecioso]

@infomiho haven't looked at anything here, but wanted to pop in; if we're going to be using dope.sh more extensively, might it make sense to migrate it to a more understandable (and less edge-casey) language? We can take advantage of the fact that node is already installed...

[infomiho]

@cprecioso I think that the natural journey of all of our scripts -> inline -> bash -> Node.js

I wouldn't do it in this PR though, I'd create an issue if we agree that we want to do it.

[cprecioso]

@infomiho My vote is to even do that before this PR here. As you see fit.

[Martinsos]

+1 for the idea of rewrite at some point but also big +1 for not doing it now, priorities again, dope.sh works fine and is tested through use, no need to shake that tree at the moment.

[sodic]

This is great! It solves the most annoying and the longest part of release testing (at least to me).

I do have some questions and suggestions, check the comments.

[sodic]

We have a very similar thing in opensaas-sh/tools. Can we consolidate them and somehow?

[infomiho]

They are actually quite different:

• opensaas-sh/tools script can use the template dir it has available on the disk
• template-test/toolsscript needs to run wasp new each time to get the template

[infomiho]

[sodic]

Ok, fair enough.

I thought the differences were maybe coming from us forgetting to do some stuff in one of the scripts (e.g., the trap thing). But if they're that different because they really are different, then all good.

RAW.

[sodic]

Looks great!