Quote posting when?
What if you could keep using the tools built for your needs while opening them to your community or the broader fediverse on your terms?
With Mosaic, we partner with you to build custom Bonfire extensions that connect your existing tools to the fediverse.
📣 Details: bonfire.cafe/post/01K06RMXVE...
In metropolitana verso la libera collina di Castello #Genova
Question:
Bonfire has various tooling around interaction policies, i.e. who may see a post, who may reply to a post, etc
How does that interact with other Fediverse software, as of right now?
@LiquidParasyte we plan to test with gts interaction policies... will report on a dedicated blogpost
@metasyn Hi, you can find some info here: indieweb.social/@bonfire/114...
but here my biased TD;LR
A VPS with 8 gb RAM and if you can set-up a S3 storage at the very beginning would be great. It helps with scaling and keeping media/files organized(I’ve struggled a bit setting it up after deployment, so I definitely recommend doing it early.)
does anyone know what the minimum system requirements are for running #bonfire social are? i looked through the documentation a bit but couldn't find (maybe i missed it)
Question:
Bonfire has various tooling around interaction policies, i.e. who may see a post, who may reply to a post, etc
How does that interact with other Fediverse software, as of right now?
@ivan @LiquidParasyte The Articles feature is beautiful!!!! Love it 🤩 🤩 🤩
🚀We've just published the Bonfire Social 1.0 Release Candidate 2 . Here the full article: bonfire.cafe/pub/objects/01J...
corn cobs from a recent harvest
🚀We've just published the Bonfire Social 1.0 Release Candidate 2 . Here the full article: bonfire.cafe/pub/objects/01J...
@ivan @LiquidParasyte #HelpANoob #Feedback
I tried configuring S3 storage following what I assumed was the logical setup path. I added to the .env
file this:
UPLOADS_S3_BUCKET=bucketID
UPLOADS_S3_ACCESS_KEY_ID=my_keys
UPLOADS_S3_SECRET_ACCESS_KEY=my_secret
UPLOADS_S3_REGION=fr-par
UPLOADS_S3_HOST=s3.fr-par.scw.cloud
UPLOADS_S3_SCHEME=https
UPLOADS_S3_URL=https://bucketID.s3.fr-par.scw.cloud
Then I redeployed the app, but unfortunately, I couldn’t get it to work. I eventually reverted to the default settings (thankfully without breaking anything... i guess, jeje 😅).
is there something "obvious" that i'm doing wrong?
btw, reading the doc, I join @box464's suggestion from the Installation party, it would be great to have more detailed documentation or examples for S3-compatible setups (like Scaleway.), similar to the excellent SMTP setup guide you already provide.