kosmos/chef
kosmos/chef
8
3
Fork 0
Code Issues 28 Pull Requests 4 Projects 2 Activity

IPFS cluster mid-term solution #26

New Issue
Closed
opened 2019-04-04 08:13:52 +00:00 by raucao · 3 comments
raucao commented 2019-04-04 08:13:52 +00:00
Owner
Copy Link

Eventually, we're shutting down dev.kosmos.org, which would leave us with only one of the currently two cluster nodes.

Perhaps helpful for this, I just stumbled upon this detailed guide for setting up a cross-region cluster on the cheap:

https://gateway.ipfs.io/ipfs/QmTqD45V5EFF9DvCpr39vyJDE5m1PJYdhWSjqNdYLAgA37/

Eventually, we're shutting down `dev.kosmos.org`, which would leave us with only one of the currently two cluster nodes. Perhaps helpful for this, I just stumbled upon this detailed guide for setting up a cross-region cluster on the cheap: https://gateway.ipfs.io/ipfs/QmTqD45V5EFF9DvCpr39vyJDE5m1PJYdhWSjqNdYLAgA37/
raucao commented 2019-05-28 12:24:27 +00:00
Author
Owner
Copy Link

Thinking about this again, and I can't help but wonder why we should use a private pin orchestration mechanism, when our IPFS hashes are all published on the public Ethereum ledger to begin with.

That means any node listening to the blockchain for new hashes could just pin them from those events. With the kredits-contracts JS wrapper, that would probably be solved in less than 10 lines of code.

/cc @bumi

Thinking about this again, and I can't help but wonder why we should use a private pin orchestration mechanism, when our IPFS hashes are all published on the public Ethereum ledger to begin with. That means any node listening to the blockchain for new hashes could just pin them from those events. With the `kredits-contracts` JS wrapper, that would probably be solved in less than 10 lines of code. /cc @bumi
raucao commented 2019-06-12 10:53:37 +00:00
Author
Owner
Copy Link

https://github.com/67P/kredits-contracts/pull/136

https://github.com/67P/kredits-contracts/pull/136
raucao commented 2019-07-02 11:44:11 +00:00
Author
Owner
Copy Link

Closing this in favor of this more detailed roadmap that is being worked on at the moment: https://github.com/67P/kredits-contracts/issues/148

Closing this in favor of this more detailed roadmap that is being worked on at the moment: https://github.com/67P/kredits-contracts/issues/148
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
service
accounts
Kosmos Accounts
service
discourse
Kosmos Community Forums
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
bug
Something is not working
design
Graphic/visual design
dev environment
Config, builds, CI, deployment, etc.
docs
Documentation
duplicate
This issue or pull request already exists
enhancement
Improving existing functionality
feature
New functionality
good first issue
Dive in, and start contributing
idea
Something to consider
invalid
Not a bug
kredits-1
Small contribution
kredits-2
Medium contribution
kredits-3
Large contribution
on hold
Currently not actionable
ops
Manual IT ops activities
question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
ui/ux
User interface, process design, etc.
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bkero bumi fsmanuel galfert greg hueso raucao slvrbckt
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#26
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?