php 8.1 php8.1-xml php8.1-curl php8.1-sqlite3 composer 2.2 mailpit nodejs npm supervisor
If you already have Laravel in a git repository, then you will need to run a few things to get the code working.
- Run
npm install - Run
php artisan migrateto create database tables - Run
php artisan db:seedto create menu entries
Install Laravel in an empty repository
composer create-project laravel/laravel sonicom
or if you have already got laravel installed, then run
composer install
Set .env DB_CONNECTION=sqlite
Install Breeze - a minimal, simple implementation of all of Laravel's authentication features, including login, registration, password reset, email verification, and password confirmation.
composer require laravel/breeze --dev
php artisan breeze:install blade
Start the Vite development server to automatically recompile our CSS and refresh the browser when we make changes to our Blade templates
npm install
npm run dev
Populate database with Laravel and Breeze default tables:
php artisan migrate
Other
https://tighten.com/insights/supercharge-your-laravel-tinker-workflow/
You can create objects on the command line: https://medium.com/@miladev95/laravel-tinker-1035402993c3
You can dispatch jobs: https://dev.to/jiteshdhamaniya/dispatch-a-job-from-tinker-in-laravel-13o7
https://coding-lesson.com/creating-dynamic-nested-menus-in-laravel-with-relationships/
Managed to generate a certificate for a :80 site using the following:
certbot certonly --webroot -w /var/www/sonicom.amtoolbox.org -d sonicom.amtoolbox.org
Test renewal:
certbot renew --dry-run
There is an Ansible role 'sonicom-ecosystem' which can be used to set up the proxy and the backend web servers. This is currently in the ISF SVN repository svn-scripts
Run
npm run dev
php artisan serve
In visual studio code, start a 'Listen for xdebug' session.
You have to make sure that the xdebug module is loaded. check php -m to see if it is. You can possibly enable it by adding zend_extension=xdebug to e.g. /etc/php/8.2/cli/php.ini
Add an [xdebug] section to /etc/php/8.2/cli/php.ini with at minimum the following:
xdebug]
xdebug.mode=debug
xdebug.start_with_request=yes
You can check the xdebug information via the php command xdebug_info() (much like php_info()).
The same as for Linux
Got xdebug working with the following php.ini configuration
[Xdebug]
;zend_extension=xdebug
xdebug.remote_enable=on
xdebug.remote_autostart=1;
xdebug.log=/tmp/xdebug.log
xdebug.mode=debug
xdebug.start_with_request=yes
And the default .launch Listen for debug
{
"name": "Listen for Xdebug",
"type": "php",
"request": "launch",
"port": 9003
},
If you are pulling from master/origin you should link the post-merge hook into the .git/hooks director with:
cd .git/hooks && ln -s ../../git-hooks/post-merge post-merge
This will do the stuff necessary to update your local code, e.g. run composer install, ./artisan migrate, etc. See the file for details 'git-hooks/post-merge'
You must set the trusted proxies in app/Http/Middleware/TrustedProxies.php, otherwise URLs are not rewritten correctly
You must map the SONICOM-DATA share to storage/app/public/data
A dataset is (like for RADAR) a set of data. We use a table 'dataset' to save information about our datasets. Each dataset has a unique id and a user associated with it. The following can be used to manipulate datasets:
- Dataset model
- Dataset controller
Local datasets which may or may not have been uploaded to RADAR
- title
- description
- uploader_id
Files associated with datasets which are cached locally.
- Remove migration entry in 'migrations' table
- Drop table in your sql editor of choice
- Run migration again (php artisan migrate) which will just run those not yet in the migrations table
- Reseed using php artisan db:seed --class=<yourclassseeder, e.g. DatasetSeeder>
Note that the snap package wouldn't run the script - can't find nc-config
Modify /etc/octaverc on Ubuntu to add paths
A 'database' is a collection of data in a specific collation of formats. E.g. a collection of HRTF data, where each database record contains one HRTF and one PNG.
- It has a title
- It is uploaded/managed by one user
- It can contain any number of datasets as defined in it's dataset definition ('datasetdef').
- May be linked to a RADAR dataset
- Will be linked to visualisations and tools via its datasetdef.
A 'dataset' is one record in the database. One record may contain multiple files of different datatypes. The exact composition of a 'dataset' is defined in the database's 'datasetdef'.
A 'datatype' is one of a predefined type of data which can be assigned to a datasetdef. E.g. there may be 'HRTF', 'PNG',of 'CSV'.
- It has a title. E.g. 'HRTF'
- It may be associated tools (e.g. Sofatoolbox)
- It may be associated visualisations (e.g. octave sofa ...)
A 'datasetdef' is a definition of which datatypes are in each dataset. E.g. a dataaset may contain two different hrtfs and one png per record.
A datafile associated with a dataset. E.g. one SOFA file or one PNG
E.g. Octave
The service is started via a job and can be passed dynamic parameters. A widget can be linked to a service and specify parameters.
A widget is a way of processing and displaying data. It could be just a simple image display, or a file name / parameter listing. However, it could also be linked to a service.
Log files are found in laravel/storage/logs
- reverb.log
- worker.log
- laravel.log
Drop all tables and reseed database with:
php artisan migrate:fresh --seed
You can observe for database changes in an 'Observer' and dispatch a Job from that observer. An alternative would be to use a 'listener' and an 'event'.
If you want to debug a job in a queue, you need to use the 'sync' QUEUE_CONNECTION, since the php debugger won't stop in the event/listener/job code, if you use, e.g., 'database'
Filament is a framework/stack with a panel, table and form builder. This may make it much easier to create interfaces to database tables.
Create a resource for a table with
php artisan make:filament-resource Dataset --generate
Note that for the FileUpload, the upload_max_filesize php setting must be large enough!
https://dev.to/jump24/laravel-blade-components-3hbh
You can format blade templates using the following tool: https://github.com/shufo/blade-formatter
e.g. node_modules/.bin/blade-formatter --write resources/views/livewire/radar/dataset.blade.php
https://redberry.international/laravel-reverb-real-time-communication/ https://novu.co/blog/the-ultimate-guide-to-laravel-reverb/
Event classes appear to need to the 'implements ShouldBroadcast'.
https://laraveldaily.com/post/filament-v3-nested-resources-trait-pages https://github.com/GuavaCZ/filament-nested-resources https://laraveldaily.com/post/nested-resource-controllers-and-routes-laravel-crud-example
These services must run for everything to work:
The reverb server should be running via supervisorctl
You can deploy to the test server http://sonicom-test.kfs.oeaw.ac.at which will do a composer install and artisan migrate:fresh --seed in the post-receive hook
git push sonicom-test
XML Schema: https://www.radar-service.eu/schemas/descriptive/radar/v09/radar-elements
Create a model with it's migration and seeder with the following command:
./artisan make:model -m -s <modelname-in-the-singular>
You can create a Livewire form and component (https://fly.io/laravel-bytes/livewire-3-forms/) so you can submit the form without leaving the page.
URL: https://sonicom.amtoolbox.org Host: ubuntu-vm-1.kfs.oeaw.ac.at
The following ports should be open:
Note: these ports were open on ubuntu-vm-1 before debugging with Gerhard Bauer:
root@ubuntu-vm-1:~# ufw status Status: active
To Action From
22/tcp LIMIT 193.171.195.0/25 # Ansible role linux-defaults ISF SSH (default) 22/tcp LIMIT 10.4.245.0/25 # Ansible role linux-defaults ISF SSH (default) 22/tcp LIMIT 10.4.21.0/24 # Ansible role linux-defaults ISF SSH (default) 80/tcp ALLOW Anywhere # Ansible role apache2 HTTP 443/tcp ALLOW Anywhere # Ansible role apache2 HTTPS 3389 ALLOW 10.4.21.0/24 # Ansible role linux-defaults RDP (ubuntu-vm-1) 3389 ALLOW 10.4.245.0/25 # Ansible role linux-defaults RDP (ubuntu-vm-1) 3389 ALLOW 193.171.195.0/25 # Ansible role linux-defaults RDP (ubuntu-vm-1) 1022 ALLOW Anywhere 8000 ALLOW Anywhere 5173 ALLOW Anywhere 2049 ALLOW Anywhere 111 ALLOW Anywhere 8080 ALLOW Anywhere 8081 ALLOW Anywhere 1433 ALLOW Anywhere 80/tcp (v6) ALLOW Anywhere (v6) # Ansible role apache2 HTTP 443/tcp (v6) ALLOW Anywhere (v6) # Ansible role apache2 HTTPS 1022 (v6) ALLOW Anywhere (v6) 8000 (v6) ALLOW Anywhere (v6) 5173 (v6) ALLOW Anywhere (v6) 2049 (v6) ALLOW Anywhere (v6) 111 (v6) ALLOW Anywhere (v6) 8080 (v6) ALLOW Anywhere (v6) 8081 (v6) ALLOW Anywhere (v6) 1433 (v6) ALLOW Anywhere (v6)
https://codewithhugo.com/alpine-tips/
https://codewithhugo.com/alpinejs-x-for-with-objects/
Error "Spatie\Permission\Exceptions\PermissionAlreadyExists" when running ./artisan migrate:fresh --seed
If, when running ./artisan migrate:fresh --seed, you get the error 'Spatie\Permission\Exceptions\PermissionAlreadyExists', you can fix this by running the following:
./artisan cache:forget spatie.permission.cache
./artisan cache:clear
Jonnie uses git attibututes and smudge/clean filters to convert to 4 space tabs when committing code. Added *.blade.php filter=tabspace4 to .git/info/attributes file.
We're using Tailwind CSS.
If you want to convert a HEX color into a Tailwind color, you could use this site: https://nearest-tailwind-color.netlify.app/
Modified by Jonnie