Pertempto
commented
2 months ago @DavidLandes I bought the domain name kwila.cloud a while ago - I have been planning to use it as a place for hosting free personal apps for people to use.
I was originally planning on making it with pretty much the same tech that I used for kookaburra.cloud, but a lot of that tech is very much vendor-specific - a lot of firebase stuff.
Maybe I should look into using more common/open technologies to setup kwila.cloud? If we use the same basic idea of the K api and packages I have been working on for Kookaburra, we could save ourselves a lot of duplicate work in the long run. We could probably write the apps in such a way that they could run locally, on Kwila, and on Kookaburra. The main thing to make that work would be removing a lot of the limitations that the Kookaburra environment puts in place but I'm totally fine with pursuing that on my own time.
How would you feel about this? You have no stake in Kookaburra so I don't want my interest in Kookaburra to bias how we design our el-apps system. However, we could end up saving ourselves a lot of duplicate work long term if I open sourced the K api and packages and transformed Kookaburra more into a specific hosting platform for open source apps. I'm thinking this would be very similar to how Gitlab community edition is open source but they make their money by selling the SaaS to businesses.
This is probably a conversation that we should have face to face, there's a lot of pieces involved😆
How will we host our apps on the internet?
It would be ideal to implement all our apps in a way that they could be self hosted for those that want that kind of thing. However, our target users aren't necessarily going to be very techy, and if our apps are going to be of any use to them then we need to have some sort of publicly hosted version of each app.