measure this ceppa bryan johnson...
noemamag.com/cultivating-wel...
nuova casa per le galline in costruzione, per questi giorni devono accontentarsi di un bilocale...
I've noticed that as well when I edit posts. The Bonfire Edit dialog isn't quite right. I usually just delete it and start over.
@ele@spark.box464.social @spark464@spark.box464.social @mayel @box464@mastodon.social @admin@spark.box464.social
right, we need to properly integrate the edit workflow in our current composer, instead of using a dialog... will open an issue! thx!
noticing is my way of opposing
"[...] Noticing is my way of opposing a particular modernist practice of looking towards an imagined future. Certain things get coded as possible futures and then we develop blinders so that all we can see is our trajectory towards one kind of imagined future, which isn’t actually the future but is a stereotyped dream future. And so, we stopped seeing. Noticing is trying to take those blinders off to look at the world around us, with special attention to the more-than-human world, by which I mean the human plus non-human world."
Non so bene cosa stiamo facendo ma per ora sembra piacergli....
Anna Tsing - Wonder in the midst of dread (A very recent lecture)
Exploring a Bonfire Geosocial Extension
🤮 This is the reason why US withdraws from UNESCO today (from the official note)
"...UNESCO’s decision to admit the “State of Palestine” as a Member State is highly problematic, contrary to U.S. policy, and contributed to the proliferation of anti-Israel rhetoric within the organization."
state.gov/releases/office-of...
Looking at @bonfire I feel like it's time to setup a test instance?
@ankorage@fe.disroot.org @muppeth@fe.disroot.org sounds awesome!
"... According to Young's notes, the song was banned in Spain under Franco. according to Xavier Valiño, when Zuma was released in Spain following Franco's death, the song was listed as "Cortez, Cortez"."
https://www.youtube.com/watch?v=x-XnPXL_HMA
Connect your existing tools to the fediverse with Mosaic
Don't the captcha people understand that by now we're not selecting motorbikes or fire hydrants but what we think the algorithm thinks other people think they are?
in love with the new #BrandeeYounger album
@stefan@gardenstate.social edited, thanks! the link is opencollective.com/bonfire-n...
Man, this is so exciting! I've been thinking about building with Bonfire for a while now, this might be the push I need!
@sean@deadsuperhero.com great, let's conspire together 🔥
🔥 Bonfire Social 1.0 RC2
@ozoned@social.ozoned.net Thanks for sharing! That was very useful to watch even if painful at times (mostly because I wanted to jump in with pointers but it was prerecorded :D). I took many notes of things to improve with the documentation and tooling.
Overall, the docs and tooling for deploying directly with docker (compared to those using @coopcloud@social.coop which is the recommended and simpler approach) are out of date and too complex mostly because they've been adapted from the dev ones, and we're thinking about how to offer an alternative method with only a compose file and a .env (though I'd welcome advice about how to do so in a simple way, as the just commands are mostly there to reduce the guide to a handful of steps/commands instead of having to copy paste a lot more, and they also set some variables used in the compose file to make it more flexible, but maybe that's not worth it, or there are some other ways to simplify?)
Here's some hints on the main blockers you encountered:
- you first entered
MIX_ENV=emberwhen you wantedFLAVOUR=ember - if you enter
ctrl+c iniex it pauses the app so it wouldn't respond unless you unpause it (by pressing c for continue) - we recently closed port 4000 which now not open outside of docker's internal network by default (for security since you usually want people to connect through the web proxy in prod) and need to update the docs
- we need to better document that it's also running a web proxy by default on ports 80/443, and point to where the caddy config is
- at one point you were looking at
docker-compose.ymlinstead of the release onedocker-compose.release.yml - during of the following attempts where you tried to run dev you were still following the prod guide instead of the dev guide which uses different just commands and env vars
I'm not sure why you weren't able to connect on port 80 during the first attempt though, as the elixir app logs didn't show anything, and caddy's error log was pretty cryptic, I'd be curious what you'd see on port 4000 if you opened it in docker-compose.release.yml
ah thinking about it more, one of your viewers may have guessed the issue, saying you had to set up a domain and set the hostname. As port 80 redirects to port 443 and that one couldn't work without those.
Attempted to set up @bonfire a couple of times and didn't have success. But hopefully someone can find this valuable and/or tell me what I did wrong to help me learn as well.
https://video.firesidefedi.live/w/sXNGDdqurg59cE3syZ3svU
#peertube#vod#tech#bonfire#fedi#fediverse#it#install
@ozoned@social.ozoned.net Thanks for sharing! That was very useful to watch even if painful at times (mostly because I wanted to jump in with pointers but it was prerecorded :D). I took many notes of things to improve with the documentation and tooling.
Overall, the docs and tooling for deploying directly with docker (compared to those using @coopcloud@social.coop which is the recommended and simpler approach) are out of date and too complex mostly because they've been adapted from the dev ones, and we're thinking about how to offer an alternative method with only a compose file and a .env (though I'd welcome advice about how to do so in a simple way, as the just commands are mostly there to reduce the guide to a handful of steps/commands instead of having to copy paste a lot more, and they also set some variables used in the compose file to make it more flexible, but maybe that's not worth it, or there are some other ways to simplify?)
Here's some hints on the main blockers you encountered:
- you first entered
MIX_ENV=emberwhen you wantedFLAVOUR=ember - if you enter
ctrl+c iniex it pauses the app so it wouldn't respond unless you unpause it (by pressing c for continue) - we recently closed port 4000 which now not open outside of docker's internal network by default (for security since you usually want people to connect through the web proxy in prod) and need to update the docs
- we need to better document that it's also running a web proxy by default on ports 80/443, and point to where the caddy config is
- at one point you were looking at
docker-compose.ymlinstead of the release onedocker-compose.release.yml - during of the following attempts where you tried to run dev you were still following the prod guide instead of the dev guide which uses different just commands and env vars
I'm not sure why you weren't able to connect on port 80 during the first attempt though, as the elixir app logs didn't show anything, and caddy's error log was pretty cryptic, I'd be curious what you'd see on port 4000 if you opened it in docker-compose.release.yml
we have 3 years to create a common transnational infrastructure to defeat Elon Musk American party