senooken JP Social
  • FAQ
  • Login
senooken JP Socialはsenookenの専用分散SNSです。
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Conversation

Notices

  1. h3poteto (h3poteto@pleroma.io)'s status on Saturday, 17-May-2025 18:01:23 JST h3poteto h3poteto
    https://blog.digger.dev/does-diggers-orchestrator-backend-need-to-be-accessible-publicly/

    > This configuration, however, won't have certain features such as concurrency, has a potential for clashing applies, and there's a need for manual setup of buckets or tables for PR-level locks.

    backend-lessだとPR-level locksは使えないのかなー
    In conversation about a month ago from pleroma.io permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: blog.digger.dev
      Does Digger’s Orchestrator Backend need to be accessible publicly?
      We often get asked this question. The answer is simple - the orchestrator backend for Digger does not necessarily need to be publicly accessible, but it does need to interact with GitHub to trigger CI jobs. So basically, whether you choose to self-host Digger or use the managed Digger Cloud

    Feeds

    • Activity Streams
    • RSS 2.0
    • Atom
    • Help
    • About
    • FAQ
    • TOS
    • Privacy
    • Source
    • Version
    • Contact

    senooken JP Social is a social network, courtesy of senooken. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.

    Creative Commons Attribution 3.0 All senooken JP Social content and data are available under the Creative Commons Attribution 3.0 license.