forked from Fediversity/meta
add notes on user-facing architecture
This commit is contained in:
parent
54eecb1150
commit
6ee8279af6
|
@ -1,16 +1,36 @@
|
|||
Attendees: Kevin, Koen, Valentin, Robert, Ronny
|
||||
|
||||
* Koen:
|
||||
* Björn is getting on board thsi week to help with communications until at least March 2025
|
||||
* Björn is getting on board this week to help with communications until at least March 2025
|
||||
* Robert:
|
||||
* Completed the planned improvements to logging
|
||||
* Managed to deploy a service via Proxmox from scatch yesterday
|
||||
* (rehashing progress of the past week)
|
||||
|
||||
Availability in the next weeks:
|
||||
* Nicolas: about 4.5 days/ week
|
||||
* Valentin: 5x .5 day/week
|
||||
* Robert: 3x .5 day/week
|
||||
* Koen: 4x .8 day/week + 1x .5 day/week
|
||||
* Ronny: 4x .2 day/week
|
||||
* Kevin: 5x .5day/week
|
||||
* Nicolas: about 4.5 days/ week
|
||||
* Valentin: 5x .5 day/week
|
||||
* Robert: 3x .5 day/week
|
||||
* Koen: 4x .8 day/week + 1x .5 day/week
|
||||
* Ronny: 4x .2 day/week
|
||||
* Kevin: 5x .5day/week
|
||||
|
||||
# Working session: Architecture discussion
|
||||
|
||||
Attendees: Robert, Valentin, Koen, Kevin
|
||||
|
||||
- Robert: NixOps should handle backup creation and restore, since it knows all the details for that
|
||||
- There will be an interface to plug Nix expressions with scripts that can access all the resources
|
||||
- Once should be able to build domain-specific applications around that
|
||||
- Valentin: Backups seem to be morally equivalent to deployments "to a file"
|
||||
- Koen walked us through myprotagio.nl
|
||||
- Kevin will share source code with Valentin
|
||||
- It's a role-based-permission and billing UI wrapping PowerDNS, Postfix Admin, and InvoiceNinja
|
||||
- Written in Laravel and Tailwind
|
||||
- To build a UI for deployment we'd primarily need a REST API to a database
|
||||
- Primary work would be to do the architecture and design
|
||||
- Valentin: Maybe we could add just the APIs for the deployment workflows from a completely new service, and connect the front-end to that
|
||||
- Won't have to touch the PHP then
|
||||
- But for the full integration to work one will have to understand the whole system anyway
|
||||
- At that point one may as well keep maintaining it or rewrite it
|
||||
- Koen: The existing thing needs work regardless, and would like to move away from PHP to Python anyway
|
Loading…
Reference in a new issue