Multi user support in tmp path

[SrZorro]

trafficstars

Changelog

• Changed all references from /tmp/caxa to /tmp/caxa/<username>
• Tests updated to use path with username (/tmp/caxa/<username>/[tests|examples])
• /tmp/caxa directory is set with 777 permissions
• /tmp/caxa/<username> is set with 700 permissions
• All current tests pass ✅ in multi user testing with a little bit of manual help
  • In my dev setup I used docker to build the stubs and manually run the tests with 2 users, im not sure how we can test it correctly with index.test.ts as we need to switch users during the test, what are your thoughts on this matter @leafac ? With a bit of docker we can test multi user in linux, Windows containers could be an option to test windows, but for Mac I don't have a good option yet. Also you can only run windows containers in windows, and not at the same time as linux containers (you have to switch engines with DockerCli.exe -SwitchDaemon)

Fixes #53

[leafac]

Commented on testing here: https://github.com/leafac/caxa/issues/53#issuecomment-1115945380

Again, excellent work on this. I really appreciate how you covered all the bases with tests, the different kinds of stub (Go & shell script), and so forth.

I’ll wait to hear back from you on my approach to testing (in summary, do manual testing because automated tests may not be worth it), and then I’ll work on merging this.

[leafac]

Hi @SrZorro,

First of all, thank you very much for your contribution! I appreciate the time you took into using caxa, understanding the packaging architecture, and contributing with these tweaks.

I’ve been thinking about the broad strategy employed by caxa and concluded that there is a better way to solve the problem. It doesn’t include a self-extracting executable, so it subsumes this pull request.

It’s a different enough approach that I think it deserves a new name, and it’s part of a bigger toolset that I’m building, which I call Radically Straightforward · Package.

I’m deprecating caxa and archiving this repository. I invite you to continue the conversation in Radically Straightforward’s issues.

Best.