diff --git a/CHANGELOG.md b/CHANGELOG.md index 30ea40de4ccc00c508e17278c61c167f239d13ed..8fc0566dfdf0880c210d9ff72c737716200ad0e8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,5 @@ # Changelog -## 0.0.1 +## 1.0.0 * Initial release diff --git a/README.md b/README.md index a4aaa4596a48923dd11f961cb7f35d68d683e904..8a264f556ae8285e9932d015f204e1994ed412af 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,3 @@ -## Trigger post deploy - -``` -curl -G -X POST --data-urlencode token="<token>" https://<your domain>/send-note -``` - # License This project (excluding post content itself) is released under the Apache License v2 @@ -130,6 +124,23 @@ Just copy and paste the iframe result into the /layouts/partials/microblog_ifram All that is left now is to push your code to your GitLab repo. At that point the .gitlab-ci.yaml file should automatically do the rest. After a few minutes you should have a running static site with full ActivityPub support. Enjoy. -# Development notes +# Development Here is some information about how to do some processing on the serverless functions in the /api folder: https://vercel.com/docs/functions/serverless-functions/runtimes/node-js + +To obtain the source simply clone our git + +```bash +git clone https://git.qoto.org/fedipage/fedipage +``` + +## Trigger post deploy + +Typically every 5 minutes the server will call send-note automatically. However +you can trigger it manually with the following code. + +``` +curl -G -X POST --data-urlencode token="<token>" https://<your domain>/send-note +``` +Keep in mind the POLL_MILLISECONDS env variable acts as a guard against this +being called too often. You will need to set this to a low value for debugging. diff --git a/api/nodeinfo/2.1.ts b/api/nodeinfo/2.1.ts index 86d1cfdefbcaeb3bf65d5e4981feb11da32489a8..f48d92978862614f8dae4714948829906b929e33 100644 --- a/api/nodeinfo/2.1.ts +++ b/api/nodeinfo/2.1.ts @@ -9,7 +9,7 @@ export default function (req: VercelRequest, res: VercelResponse) { "name": "Fedipage", "repository": "https://git.qoto.org/fedipage/fedipage", "homepage": "https://fedipage.com/", - "version": "0.0.1" + "version": "1.0.0" }, "protocols": [ "activitypub" diff --git a/content/news/2023-10-11-fedipage-v1-released.md b/content/news/2023-10-11-fedipage-v1-released.md new file mode 100644 index 0000000000000000000000000000000000000000..eb88613f91c523a784b73ee14df4812ceb1e9e27 --- /dev/null +++ b/content/news/2023-10-11-fedipage-v1-released.md @@ -0,0 +1,44 @@ +--- +slug: fedipage-v1-released +date: '2023-10-10T02:36:48Z' +title: Fedipage, ActivityPub for Static Sites, has Released v1 +tags: +- Release +draft: true +--- + +The moment you have all been waiting for, v1 of Fedipage has just been released. +This is our first version, so consider it as a beta, but it is fully functional. + +You can find the release on our GitLab here: + +Here is what we have accomplished so far: + +* Moved almost all site-specific stuff into configuration variables to make form + easier install. +* Organized the layouts/partials so that it is very easy to update the + the templates. +* Requires Vercel and Firebase for *full* ActivityPub support but will provide + limited support as a purely static site as well. Limited support means the + account can be seen, and its posts, but following wont be confirmed. +* Wrote detailed step-by-step install instructions to make it easy for everyone. +* Supports the following ActivityPub features: +** Following confirmation +** Notifications in your feed when new posts are made +** The various pages show content from the fediverse interacting with it like + reboosts, likes, and even replies which show up as comments on the page. +* Tags are supported with a few options: +** Tags can be configured to automatically be added to every post. +** The tags added int he front-matter of a post can be added as fedivese tags. + This can be set independently of any default tags. +** Tags can be rendered invisibly, not showing in the text of the post on the + fediverse yet still contain the tag metadata for searches +* An ActivityPub alias can be set if you have other accounts across the + fediverse. The alias can also allow you to migrate existing followers to + the web page (untested, proceed at your own risk). +* Microblog side-panel can be configured to show content from your alias + fediverse account. +* Multiple categories of blogs can be handled simultaniously and categorized and + tagged independently. +* Front page is constructed from markdown and broken up into short codes. So + the front page can be modified without touching the html.