Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API spec for Distributed Press #23

Closed
3 tasks done
benhylau opened this issue Nov 25, 2020 · 3 comments
Closed
3 tasks done

API spec for Distributed Press #23

benhylau opened this issue Nov 25, 2020 · 3 comments
Assignees
Labels
COMPOST: Technical Magazine software and website development

Comments

@benhylau
Copy link
Member

benhylau commented Nov 25, 2020

🎟️ Re-ticketed from: #
πŸ“… Due date: N/A
🎯 Success criteria: Create clear API spec for Distributed Press and document their behaviour.

Task Summary

Distributed Press is expected to have a modular and extensible API spec to serve its various features for DWeb publishing. This may look like:

These can be served from api.distributed.press/<project> to start, but should be portable to any host. See https://github.com/hyphacoop/api.distributed.press

To Do

  • Draft API spec for basic actions
  • Publish response schema
  • Publish as .md file in appropriate repo
@benhylau benhylau added the COMPOST: Technical Magazine software and website development label Nov 25, 2020
@benhylau benhylau self-assigned this Nov 25, 2020
@benhylau benhylau added this to To do in Distributed Press & COMPOST via automation Nov 25, 2020
@benhylau
Copy link
Member Author

benhylau commented Nov 25, 2020

Short-term

#18 should POST static.tar.gz to /v0/publication/static/compost/?domain=one.compost.digital&apikey=API_KEY and Distributed Press would automatically untar, cp the directory to WWW root on our server and async pin it on ipfs and hypercore.

Long-term

In order to serve plain-text content (e.g. markdown assets) for #21 we'd want assets.tar.gz to do something like /v0/publication/jekyll/compost/?domain=one.compost.digital&apikey=API_KEY so we not only untar, but also build the assets before cp'ing to the WWW root.

This way, we can process our plain text assets to fulfill API requests like /v0/content/markdown/compost/ that returns plaintext versions of our articles, with metadata such as their sig, ipfs CID, etc.

@benhylau benhylau moved this from To do to In progress in Distributed Press & COMPOST Nov 25, 2020
@benhylau benhylau moved this from In progress to Feedback Required in Distributed Press & COMPOST Dec 8, 2020
@benhylau
Copy link
Member Author

benhylau commented Dec 8, 2020

Spec drafted https://github.com/hyphacoop/api.distributed.press/blob/main/README.md and will add new actions as we go.

@benhylau
Copy link
Member Author

benhylau commented Dec 9, 2020

See for Identity and Content API re: distribution and signing:

(from @fauno @ sutty)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
COMPOST: Technical Magazine software and website development
Projects
No open projects
Development

No branches or pull requests

1 participant