Statistics on what Composer packages all of your webapps use.
A command-line process, php artisan usage:update, connects to your Bitbucket account, checks out your repositories, and loads info on all their Composer dependencies. The calculated information is cached locally in a JSON file. When browsing the webapp, the data is displayed from that cached data. To keep it up-to-date, schedule a cron to run php artisan usage:update regularly.
This app is under development, and still has several limitations:
- It can only load webapps from a single Bitbucket repository, not other hosts or from multiple.
- It can only load dependencies from Packagist or Git repos, not svn.
- When loading dependencies from Git repos, it can only find them if the package name is in the repo URL; if they don't match, it won't be found.
- The entirety of each repo is stored locally indefinitely. Need to update this to only pull down the composer.json file.
Make sure the following are installed on your system:
- Node.js, NPM, and Grunt for build script.
- Composer for PHP dependencies.
- Sass (look for the command-line section) for stylesheets.
Then:
- Duplicate
.env.example.jsonas.env.jsonand enter your Bitbucket username and OAuth connection info. - Run
sudo npm installto install the grunt packages for this project. - Run
grunt. This:- Installs PHP dependencies with
composer install. - Creates symlinks for web assets with
symlink. - Makes sure temp folders are writable with
chmod. - Generates CSS from Sass.
- Runs automated tests with
phpunit
- Installs PHP dependencies with
- Set up MAMP to point
app/endpoints/frontendto the web address you want it at. - Edit
endpoints/[backend and frontend]/.htaccess, changing the RewriteBase line to the path your app is at - When you're ready to code, run
grunt watch(it will keep running in that terminal window). It will run unit tests as code changes, and recompile CSS as Sass changes. You'll see an OS notification pop up if there are any problems.