Suggested SurvLoop Developer Work Flows

First, my first few projects on GitHub haven't had much interaction yet, and I am new to the community. Please contact me if you've got any key changes I should focus on to better invite contributions. Constructive criticism is warmly welcome.

Applying Code Changes To Running Software

When testing changes to PHP files, you generally don't need to take any extra steps to see the results in your browser. But if you edit any of the Eloquent Models, they'll need to be re-copied to the /app/Models directory with the "artisan vendor publish" below.

To test any changes to HTML in the Views folder will always need this command run from your project's root:

$ php artisan vendor:publish --force
or
$ echo "0" | php artisan vendor:publish --force

To test changes to system-level JS and CSS files, after running the above command, you'll have either load these pages in the browser or the command line:

$ curl http://localhost/css-reload

Saving the System Settings page, or forcing its refresh will also regenerate the system JS and CSS files:
http://localhost/dashboard/settings?refresh=1

That will rewrite some key files (called on most pages) which will need to be refreshing in your browser:
http://localhost/sys2.min.js
http://localhost/sys2.min.css
...and/or use your browser's hard refresh for the page your working on.