PsySH VS AppImageKit

psysh is an interactive shell that enables developers to explore and experiment with PHP code without the need to write the source code for an entire application. It provides a simple and user-friendly shell interface where you can enter PHP code and instantly observe the results. Also, psysh is a configurable tool equipped with various plugins and modules. Therefore, you can customize it the way you want.

Tinker is a REPL built over psysh which is a general-purpose REPL for PHP. Since a Laravel application is not plain PHP and has states, databases, caches, events, and many more complex resources specific to the framework, it's not possible to interact with the application the way one would expect just using psysh.

Why choose when you can have both in one https://psysh.org/ lol... I testdrove it once, but not convinced (I think the "merged" 2-languages-in-1 is pretty funny but maybe it works for some people).

Would love to see https://psysh.org incorporated in core.

It does! Or rather it used to (and still does for some things) but looks like it broke for stdout and return value dumping a couple of years ago.

PsySH offers a dev console and interactive debugger for PHP projects. In effect, this repo creates a REPL platform for PHP developers.

psysh is a killer tool in situations like this.

And detail more on executing it: https://github.com/bobthecow/psysh/wiki/Usage

Yes, check out psysh https://psysh.org

What you're looking for sounds like AppImages (https://appimage.org/) . I have only used them while downloading games from itch.io, etc. (since i prefer package managers) but they seem to work out of the box on popular distros.

Ideally a new instance of the application is installed for each user. This also provides better isolation if one user upgrades/removes/breaks their application instance. I, for one, have really come around to the AppImage model [0] in the last couple of years.

[0] https://appimage.org/

I found a similar issue on github and tried this solution but still getting the same error .

There is AppImage[1], which packs a lot of stuff into a SquashFS filesystem, appends it to the executable, so everything is in one file.

[1] https://appimage.org

Nah i think yall just hating appimage. Real gold standard.

Although I haven't used plugins feature myself yet, this does sound like the perfect use case for them. Not every patient needs to access every single source. With plugins you can load only the source (or few sources) that they actually need. You can still use something like https://appimage.org/ to give them "a single binary", but will actually contain your slim binary and all the plugins.

```dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information```

This doesn't look like a squashfs image. Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage  if you run it with the --appimage-extract option.  See https://github.com/AppImage/AppImageKit/wiki/FUSE  for more information open dir error: No such file or directory

appimages. Appimages are similar to flatpaks, exept that they are a file you download and double click to run. Think of them as portable softwares like windows has (portable apps). They are sandboxed too. You can learn more about appimages here