#known 2020-02-13
2020-02-13 UTC
[chrisaldrich], [tantek], [LewisCowles], [snarfed], [fluffy], [jgmac1106], [Michael_Beckwit, [dmitshur], [jeremycherfas], [xavierroy], [grantcodes], [Rose] and jbove joined the channel
[KevinMarks], tsrt^, [Rose], [dmitshur], [jgmac1106] and [datashaman] joined the channel
# 
[jgmac1106] awesome, hope you enjoyed time disconnectex
[KevinMarks], mapkyca, [schmarty], [Rose], [tantek], [chrisaldrich], [Michael_Beckwit, [LewisCowles] and [grantcodes] joined the channel
# 
[LewisCowles] oh [jgmac1106] the S3 Known, isn’t going to be part of mainline it looks like https://github.com/idno/known/pull/2687
# [LewisCowles] I’m thinking of forking and including, but as it doesn’t touch any mainline known files I can rename to heroku-known so that it’s trivial to rebase off master
# [LewisCowles] It’s a really specific use-case I think will help in that regard
# [LewisCowles] I’ve only gone and linked the wrong PR / issue
# [LewisCowles] slack and it’s preview links are not glanceable
# [jgmac1106] I have an educator discount account for AWS Educate, have a chunk of space, 100 gigs on Reclaim Hosting which I can access through cPanel and Terminal...but weary because of BitNinja issues, name.com also donated a ton of space. I wonder what/how toi spin up heroku apps there
# [jgmac1106] I also will be hiring a computer science intern as I feel this will get over my head quickly.
# [LewisCowles] heroku is a platform built atop AWS. It’s more expensive because it’s managed and has all sorts of pretty buttons.
# [LewisCowles] Installing on AWS, could avoid some of the design choices I’m making
# [LewisCowles] You could run known like it’s designed to be run, rather than re-visiting. The issue then is that at a certain size I believe the design will inherently break down as most things are assumed to be one large host, with one large filesystem
# [LewisCowles] another (perhaps unhelpful) way around would be to not handle file storage in known at all and simply link URI’s. That is incredibly unfriendly to users, but would avoid upload and export from YouTube of existing content
# [LewisCowles] I’m also mildly certain Known really likes files, so there might be bugs elsewhere if you can’t treat things as files, which was why when upgrading the aws client didn’t work for their S3 client alone, I thought. Take the stream handler and pretend it’s accessing files.
[Rose] joined the channel
# [LewisCowles] Heroku doesn’t mess with your filesystem
# [LewisCowles] It prefers you don’t either
# [LewisCowles] because single machine deploys are… problematic
# [LewisCowles] So there is no way to cleanly not alter the canonical repo. It’s not a fork, fork
# [LewisCowles] it’s some extra files while upstream won’t include them
# [LewisCowles] the maintenance burden is git rebase -i origin/master
# [LewisCowles] I’m fairly certain I can even use GitHub Actions to schedule that
# [LewisCowles] at the point there is a conflict. I should be able to retire the branch
# [jgmac1106] "I also will be hiring a computer science intern as I feel this will get over my head quickly." for the public projects.....
# [jgmac1106] this is what I do now: https://jgregorymcverry.com/installingknownonreclaimhosting
# [LewisCowles] it has a release step, but downloading, running composer, etc. No it’s so much more work
# [LewisCowles] It can run dockerfiles if you’d like to write the init script sknebel. I don’t advocate for it. It’s one file + a README.md
# [LewisCowles] vs what you’re advocating for
# [LewisCowles] which is unnecessary engineering to avoid including some files people could delete if on shared hosting
# [LewisCowles] I could move the S3 stuff into `suggest` maybe though and try to PR composer for a flag to install suggestions
# [LewisCowles] but then I’d kinda need logical groups to make it support plugins
# [LewisCowles] good plugin architecture seems to be micro-services with nifty URL’s and template hacks
[jeremycherfas], [fluffy] and [Michael_Beckwit joined the channel
# [LewisCowles] would this allow me to require the plugin?
# [LewisCowles] Would it fetch the plugins dependencies?
# [LewisCowles] updated PR to S3 plugin to follow pattern
# [jgmac1106] Yes
# [jgmac1106] For those plugins that are updated. I can help with that for [mapkyca] made easy to follow instructions
# [LewisCowles] so until the plugin is registered with packagist, there will likely be issues using the README.md instructions which I did update.
# [LewisCowles] Once it is, it should also help keep known lean'ish, and clean'ish like [mapkyca] asked for; but doesn't get around the need for a repo for heroku deploys, which is effectively a fork of known.
# [LewisCowles] Although it would now only be one file, composer.json that would be different if this can be upstreamed
# [LewisCowles] I've also updated the ENV config patch so nearly everything has branded ENV 🙄 seemed to be the only feedback on it