This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-07
Channels
- # announcements (2)
- # babashka (34)
- # beginners (114)
- # biff (7)
- # calva (16)
- # cider (2)
- # clj-kondo (46)
- # clj-on-windows (14)
- # clojars (13)
- # clojure (33)
- # clojure-europe (17)
- # clojure-nl (2)
- # clojure-norway (8)
- # clojure-spec (3)
- # clojure-uk (3)
- # clojurescript (25)
- # community-development (1)
- # datalevin (1)
- # emacs (53)
- # fulcro (31)
- # gratitude (2)
- # jobs (1)
- # lambdaisland (12)
- # lsp (57)
- # malli (3)
- # nbb (1)
- # off-topic (92)
- # pathom (2)
- # pedestal (2)
- # releases (5)
- # shadow-cljs (25)
- # sql (3)
- # squint (1)
- # testing (6)
- # vim (11)
Just tried to use the Fly Machines API, now that there (hopefully) isn't an outage anymore, and still am getting errors, albeit different ones. I've decided I'm tired of having custom theme sandboxing stuff be a blocker to getting a public instance of platypub deployed. I'm altering the roadmap: next milestone is to get platypub deployed without custom themes. themes must be installed by the site admin; if you want to add/modify a theme, you can always run your own instance of platypub (which is pretty easy at least, since you can just run it locally). I'm gonna organize the github issues in a sec, but I think what needs to happen is: • usability improvements (there are already several issues for these) • support sub domains/custom domains for netlify. currently only way to add a custom domain for your site is by going to netlify admin. however for this milestone, users of a public instance wouldn't have access to the netlify admin. and doing it through platypub is better usability anyway. By default it'd be nice to give people e.g. *.http://platypub.com domains instead of the default gibberish domains that netlify assigns to new sites. • Make sure recaptcha works without manual config for each new site • add a landing page I'll be working on the forum tutorial probably until the end of november. After that I'll work on those bullet points until completion. In the mean time, the usability improvements should be pretty accessible for anyone who wants to help out (especially once I finish updating the github issues).
> next milestone is to get platypub deployed without custom themes. themes must be installed by the site admin; if you want to add/modify a theme, you can always run your own instance of platypub (which is pretty easy at least, since you can just run it locally). I have an existing custom theme and run my own instance of platypub in production. Any changes I'll need to make to keep that running?
I guess when I said "without custom themes" I meant "without regular users being able to upload custom themes", which is already the case since they have to be installed by the site admin.
I made a Github Project thing for https://github.com/users/jacobobryant/projects/1/views/1. Looks kinda nice. maybe I'll start using projects for my other... projects Also made some slight edit's to https://github.com/jacobobryant/platypub#platypub, mostly to make it a bit more informative for people reading about the project for the first time.
(there will no doubt be plenty more issues to add, but at the moment the roadmap has enough issues to keep me and anyone else who wants to participate busy, which is all that's needed--I'll add more issues as the existing ones are completed)
Also for the meetup next week, we can knock out a couple of the things on the roadmap: https://www.meetup.com/biff-coding/events/288850026/