We could 1. Install media wiki in [[hypha]] using [[coop cloud]] (we discussed this on Monday in the TWG meeting.) Or 2. Promote your instance to ‘prod’? 1. Seems cleaner and lets us share maintenance, etc. more easily.
having said that I look forward to testing/integrating your sqlite code, and adopting your docker improvements/[[coop cloud]] implementation in agor.ai!
I am working on a presentation for Thursday but after that I hope to get my feet wet with [[coop cloud]] / [[abra]] and with that unlock setting up a variety of services for [[social coop]] and the [[agora]] community.
yesterday I focused on social.coop and it was nice — I got up our secondary server up and running with [[coop cloud]] and [[abra]], and installed a few recipes.
I plan to repoint DNS at some point to make it easier to work with [[coop cloud]]; IIUC [[traefik]] needs wiki.social.coop to point to the actual coop cloud host (hypha) to get a certificate and be able to set up the container?
thanks for taking a look :) the visual editor works fine for new pages but fails for every existing page. now I think about it, this never worked so far in wiki-alpha.social.coop either so it’ll probably be something worth fixing in the [[coop cloud]] recipe
today I’m resuming work on bringing up a https://link.agor.ai. This will be the first Agora running the closer to productionized [[coop cloud]]-based setup :)
ahoy there! yes, git is part of the usability bottleneck; the alternatives going forward seem to be roughly 1. adding more providers of identity+storage, e.g. potentially google drive/dropbox/nextcloud with oauth? or 2. make git self-hosting/community-hosting easier, and put together/develop better UI for it so more and more users can benefit from this simple decentralized hosting model. [[coop cloud]] is a great step in this direction for sure, git.agor.ai is up on coop cloud already :)