Write.as Development @writeas_dev@abunchtell.com
- Write.as
- https://write.as
- Developers
- https://developers.write.as
Admin
Casual dev-related updates from @write_as / @writefreely, tooted by @matt.
This account isn't super active. You might want to check out our other profiles!
Joined Mar 2018
Going along with this, by v1.0 we'll have built-in support for getting certificates from Let's Encrypt.
You won't need a reverse proxy in front of #WriteFreely in v0.4 -- now it can handle secure traffic on its own.
Adding basic stats to #WriteFreely About pages. https://pencil.writefree.ly/about
New task: Support changing config values via web https://phabricator.write.as/T541
@Valium@mastodon.at Yeah, Mastodon is really heavy.
Once you compile WriteFreely though, it takes up little resources. I was actually running it on a Raspberry Pi 1 with 256MB of RAM.
@Valium@mastodon.at Yeah, unfortunately the ActivityPub code needs a ton of RAM to compile right now -- the library is huge. Someone else couldn't get it to compile on a 2GB VPS.
Will hopefully fix that in the future, but for now this would be the way to go.
@Valium@mastodon.at On my regular machine, I compiled with:
env GOOS=linux GOARCH=arm GOARM=5 go build
And then transferred the binary and the directories: static, templates, pages, and keys. Then on the Pi, ran the setup process like normal.
What parts didn't work for you?
Another idea it made me think of: what if instead of comments right now, mentions just forwarded to a connected Mastodon / Pleroma / whatever account? Not sure how that'd technically work, but might have to look into it.
Recent @matt blog post getting sent around the fediverse reminded me this is pretty critical for #WriteFreely v1.0: blog data caching.
Write.as Development
boosted
Got both of these finished -- really pleased about the admin page editing functionality, in particular. Will be much better for people starting up their own instances, and customizing it how they like.
Tomorrow I'll release #writefreely v0.3.
That's two Mondays in a row, so maybe I'll keep up the weekly release schedule until we reach v1.0
All important reported issues are out of the way for v0.3 🎊
So now it's time to get some *new* features into #writefreely before this next release:
- Setting a `created` date when publishing a new post (good for importing and scheduling posts) - https://phabricator.write.as/T532
- Maybe the ability to edit some standard pages on multi-user instances, e.g. the About and Privacy pages - https://phabricator.write.as/T533
Yeah, this probably has to do with how Masto handles the `Delete` activity. Going to leave it out for now.
Today, bouncing between this and a new @matt blog post about ActivityPub identities.
Testing federation while moving posts from draft / anonymous to a blog, or vice versa, or from one blog to another.
Moving between draft and published is good so far, though re-publishing doesn't seem to have an effect on Mastodon's end.
Added an admin option to reset user passwords by running:
writefreely --reset-pass <username>
On the develop branch now, to be released in v0.3.
While it won't be required for installation, we will support Docker: https://phabricator.write.as/T531
Write.as Development
boosted
@wakest No problemo 👍
- Write.as
- https://write.as
- Developers
- https://developers.write.as
Admin
Casual dev-related updates from @write_as / @writefreely, tooted by @matt.
This account isn't super active. You might want to check out our other profiles!
Joined Mar 2018
Write.as Development's choices:
