Local dev using Just

[naterfute]

Adds local development using Just a Makefile alternative.

Fully automated from start to finish to make it easier to start developing on blueprint.
As long as I can get some people to verify this works I'll be adding support for Extension development from this file as well.
To get started you can just run the just command and it will work, after that you can just startup the dev environment using just dev and it should setup the tmux window with all 3 tasks,

Default credentials are
Username: dev
Password: dev

The following packages are required to make it work
If you lack any of them it won't even clone the repo

• Just(Obviously)
• git
• docker
• php
• composer
• yarn
• mariadb-clients
• inotify-tools
• tmux
• rsync

[prplwtf]

I'm assuming the development environment is mostly oriented towards Linux users right? The "inotify-tools" package gives me flashbacks of trying to make bashatime compatible with MacOS. (There's no good inotify-tools alternative for file watching on MacOS is there.)

[naterfute]

Man, you're right, I thought it did work with Mac. I was wrong. I'll change it to use chokidar, I thought I was being clever.

[prplwtf]

Trying the stuff out now. So far on my Arch Linux machine:

1. It seems to create a .blueprintrc in the working directory, though this isn't gitignored.
2. It does not create a pterodactyl/ folder, which causes shenanigans to.. well.. not work. Oh I see, I'm stupid, I didn't run the just command 🤦.
3. It doesn't download node dependencies.
4. In the final like DEVELOPMENT.md or something, the user should also know that they need to install some php extensions as well.
5. As far as I can tell, it doesn't run Blueprint's setup script, which Blueprint will sometimes yell at you for. It does, not sure why the version is set to "unknown", might be some fuckery I did somewhere.

I'm honestly not sure how we are going to do MacOS support, considering the nature of the Blueprint CLI being in bash. WSL should work for Windows, though.