| customer | number | Invoice number | Invoice total | Payment source | Payment total | Payment amount allocated to this invoice |
|---|
Erik Huelsmann ehuelsmann
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/bin/bash | |
| URL=https://example.com/ehuelsmann | |
| METADATA='<abc /><def>ghi</def><jkl mno="pqr" />' | |
| VMNAME=abc | |
| virsh medatada $VMNAME --uri $URL --key xyz --set "$METADATA" | |
| virsh metadata $VMNAME $URL xyz |
In order to continue on our path of development with the browser pages, we need to decide on the services structure rather sooner than later (rather, since I'm building new pages: now).
The goal of having a webservice API is to allow development of a broader ecosystem of service-using applications. In addition, we're more and more moving to a rich browser-based webapplication ourselves; rich-client web application frameworks expect to integrate with a backend service through web-services.