Skip to content

Use 🛻 pickup to handle pinning service requests #2309

@olizilla

Description

@olizilla

Review the api env, db schema, and cron jobs to find out what needs to be updated to have the api use pickup to handle pinning service requests.

TODO

  • update api/src/routes/pins-add.js to specify ElasticIpfs as the service when calling createUpload
  • update api/src/routes/pins-replace.js to specify ElasticIpfs as the service when calling createUpload
  • update cron/src/bin/pins.js to add a cluster client configured to hit pickup.
  • update cron/src/jobs/pins.js to add ElasticIpfs to the list of Clusters to check
  • update cron/src/bin/pins.js to add a check pin statuses on pickup for via status.all
  • add staging worker env var for CLUSTER_API_URL set to staging pickup url
  • remove staging worker env var for CLUSTER_SERVICE
  • add prod worker env var for CLUSTER_API_URL set to prod pickup url
  • remove prod worker env var for CLUSTER_SERVICE

note: the env var CLUSTER_SERVICE takes precedence over CLUSTER_API_URL, so we can add a value for CLUSTER_API_URL whenever we like, and then delete the CLUSTER_SERVICE env var when we are ready for to make the switch.

Parent: web3-storage/pickup#68

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementA net-new feature or improvement to an existing featureneed/triageNeeds initial labeling and prioritization

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions