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.
Copying Code Updates Into PlaceI like to keep my repositories connected to GitHub in a separate directory from the full Laravel installation, etc. So I keep a shell script handy to copy updates from my working directory to the local virtual server, e.g. repopush.sh:
$ #!/bin/bash set -x cp -r ~/repos/survloop/src ~/homestead/code/survloop/vendor/wikiworldorder/survloop/ cp -r ~/repos/survlooporg/src ~/homestead/code/survloop/vendor/wikiworldorder/survlooporg/
So each time I make edits to the code base, I run this script:
Applying Code Changes To Running Software
If you are only testing edits to Controllers, then the above step will apply the changes. But if you make any changes to Views or Models, you will need to also re-publish those files for the extra copies needed.
So you will very often need this command run from your project's root:
$ php artisan vendor:publish --force or $ echo "0" | php artisan vendor:publish --force
If you wanted, you could add this to the shell script and run it any time.
Updating System JS & CSS
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://openpolice.local/css-reload
... or saving the System Settings page, or forcing its refresh will also regenerate the system JS and CSS files:
That will rewrite some key files (called on most pages) which will need to be refreshing in your browser:
...and/or use your browser's hard refresh for the page your working on.