Publishing Updates about website HOT 9 CLOSED

Hey,
in lack of good publishing tooling I'd suggest we point the datatogether.org dnslink record to a domain that you control, e.g. we could set it to dnslink=/ipns/b5.example.net, and by setting TXT _dnslink.b5.example.net dnslink=/ipfs/somehash on that domain you can control what /ipns/datatogether.org recursively resolves too. That also nicely separates content from gateway hosting.

from website.

Update: we can now actually add more accounts to individual domains in DNSimple. So alternatively to what's described above you can also make a DNSimple account and I can invite it to manage the datatogether.org domain.

from website.

@dcwalk, absolutely! @lgierth thanks so much for the update, that'd be lovely. I'm b5 on dnssimple as well :)

from website.

:) You're all set! I made this little tool (works with an account token) for automating the record updates where neccessary: https://github.com/lgierth/dnslink-dnsimple

from website.

Hey @b5 is this something we could revisit in the coming week(ish)?
It would be great to get those artwork changes up 💃

from website.

@b5 I need an email address

from website.

ah I see. How's this for nerdy? Base64 encoded email lololol: YnJlbmRhbkBxcmkuaW8=
(my email is by no means private, just don't want robots 😃 )

from website.

Nice. Just managed to make my first publish, that CLI/script worked like a charm. Thanks for all your help @lgierth!

@dcwalk now that the most recent commit is live and we have a solid workflow for changes, feel free to let me know/PR anything that needs changing. shouldn't take more than 20 minutes to update the site to match merged PRs from here on in.

from website.

Closing this as we got this version up and running, just addressing how to best impement #30

from website.