It took me some years of conceptual work. Not completely done yet .. some functionality is not just software. But the foundation is laid…
From prompt to SaaS… loading… almost entirely build with codex
Nice!
PHP backend, yes? Small smile.
Keep up the great work. Can’t wait to see what you’re up to next!
Not yet PHP backend. The migration to the king extension is still pending.
The whole thing is part of a bigger system and also network of people who are involved.
We are getting close to 20 people and a launch is near.
Ah, I see… that king extension might make a good thread eventually too.
Twenty people is not messing around. Continued success with it!
Even a math prof - who added Bayesilisk - a tool that mathematically finds errors in permission handling and other flaws in logic, someone with a wikipedia entry for their scientific achievments, an ex Microsofty, multiple PHP internals. The team is not just a couple schoolfriends.
Even more impressive. Waiting on updates as you have the time.
Skeptic? I don’t know much about programming and other buzz words like that, but I do think PHP (programming humanly perfect) is the best language for coding…
@jochenschultz btw working on SaaS app template:
Idea: clean kernel with standard ports exposed as interfaces + libraries as adaptors implementing those interfaces (included as packages/adaptors/$port-name/$specific-implementation-adapter-name)
Wiring s done more like declarative+imports in core-routing module (so you pick the adaptors your app needs)
Domain is a library you develop on your own that interacts with kernel and ports via contracts.
This way you may switch implementations as you like and they still talk to each other (PSR from PHP philosophy).
Written in typescript (because want to be able to deploy to cloudflare).
Current modules:
- kernel
- routing
- persistency
- tenancy
- identity
- secrets store
- billing
- domain logic
- workflows
- queues
- telemetry
- middlewares
- object storage
- ai
Some others.
If you want to have a look, let me know, I’ll add you to the repo (private)
That sounds like a good start. I found the data model to be the hardest part.
Exactly that + responsibility boundaries not to be crossed by system components.