Been trying to deploy 0.11.0, but it keeps failing. Want to try this solution? We can make the environment similar and then go from there. We might need to make some other changes to actually make it work, but at least we want to make the testing similar.

Related GitHub Issues

Problem

Solution

Testing

• Added automated tests.
• Manually tested. If you check this box, provide instructions for others to test, too.

Notes for reviewers

Related GitHub Issues

Problem

This is a feature that is mostly intended for people who want to
separate their deployment code from their application code and be able
to use dependencies, a package manager, or whatever language they want.
Everything is encapsulated in a directory.

Solution

The solution is that you can change the working directory that Decaf is
running from, which then allows package managers, for example, to
reference their files in that directory, like the package.json or
deno.json file.

You do have to make sure to change your directory to go back to the
parent directory where your code probably exists. But hey, at least this
is a nice little feature for you.

Testing

• Added automated tests.
• Manually tested. If you check this box, provide instructions for
  others to test, too.

Testing the feature in this pull request by using it in our CI setup.

Notes for reviewers

This reverts commit 571f828.

Reverting because of the commit, d93032f, we no longer need to do this and using a temp directory for isolated environments has some nice benefits.
- fix: cannot validate is current_working_directory is valid input

the 0.11.0 deployment failed when we called new code that tries to check if current_working_directory is a valid option. After considering many different options. I'm opting for this one because, in the end, the validation of this input is giving a better user experience to the developer.

There is always a risk that we're going to introduce more and more issues over time. I think, actually, this permissions thing just needs an overhaul anyway, so I think it's okay to allow reading.

I think this is actually the easiest option that still provides the best developer experience.
- test: test mode isolated git environments are subdirectories to have more similar environment to real deployments

Been trying to deploy 0.11.0, but it keeps failing. Want to try this solution? We can make the environment similar and then go from there. We might need to make some other changes to actually make it work, but at least we want to make the testing similar.
- feat: specify current_working_directory where to run your scripts from (#131)

Related GitHub Issues

Problem

This is a feature that is mostly intended for people who want to
separate their deployment code from their application code and be able
to use dependencies, a package manager, or whatever language they want.
Everything is encapsulated in a directory.

Solution

The solution is that you can change the working directory that Decaf is
running from, which then allows package managers, for example, to
reference their files in that directory, like the package.json or
deno.json file.

You do have to make sure to change your directory to go back to the
parent directory where your code probably exists. But hey, at least this
is a nice little feature for you.

Testing

• Added automated tests.
• Manually tested. If you check this box, provide instructions for
  others to test, too.

Testing the feature in this pull request by using it in our CI setup.

Notes for reviewers