Fix IPFS peering #226

Closed
opened 2020-10-21 13:05:40 +00:00 by raucao · 1 comment
Owner

Since having moved the gateway to a new node, the (hacky) peering is now broken. We can use the proper peering feature in the new ipfs-go for that, instead of fixing our crontab hack.

Since having moved the gateway to a new node, the (hacky) peering is now broken. We can use the proper peering feature in the new ipfs-go for that, instead of fixing our crontab hack.
raucao added a new dependency 2020-10-21 13:06:28 +00:00
raucao added a new dependency 2020-10-21 13:06:38 +00:00
raucao added the
bug
label 2020-10-21 13:06:43 +00:00
raucao self-assigned this 2020-10-21 13:26:55 +00:00
raucao added the
kredits-1
label 2020-10-25 09:58:18 +00:00
Author
Owner

Already hot-fixed it a couple days go, by just having the cron jobs connect to barnard instead now.

Already hot-fixed it a couple days go, by just having the cron jobs connect to barnard instead now.
raucao removed a dependency 2020-10-26 08:03:31 +00:00
raucao removed a dependency 2020-10-26 08:04:15 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#226
No description provided.