A few settings.
More room for your work.

Before you start

You need a public LibCard repository and a running Feedme instance at an HTTPS address. Update both apps to versions that include the integration; older LibCard schemas reject the new settings.

In the examples below, https://support.example.com stands for your personal Feedme address. Replace it in both apps. The public site at feedme.fund is a static demo, so it isn’t your checkout server.

pnpm install
FEEDME_MODE=demo LIBCARD_REPO=example/libcard pnpm dev

crs.land → Tip Chris

Chris’s LibCard is his public profile and link catalog. Tip Chris is his personal Feedme, importing that catalog and offering picks, gift review, and Stripe checkout. Both sites are live.

These are the public Feedme settings behind that pair. For your own installation, replace the domains, handle, site name, and repository with yours:

PUBLIC_URL=https://crs.tips
SITE_NAME="Tip Chris"
BLUESKY_HANDLE=crs.land
LIBCARD_REPO=crs48/LIBCard
LIBCARD_REF=main

You can inspect the LibCard source configuration and Feedme’s public catalog and pick totals. The public endpoint includes no supporter identities, private notes, or individual payment amounts.

The import works without card-side tip buttons. To add those buttons and read public pick totals back into a LibCard, follow the optional LibCard settings below.

Explore the live example → or try simulated tips in the demo. Completed checkouts on crs.tips are real payments.

Point Feedme at your card.

Add these public settings to your Feedme server’s environment alongside its existing live configuration, then restart it:

PUBLIC_URL=https://support.example.com
BLUESKY_HANDLE=you.bsky.social
LIBCARD_REPO=your-name/your-libcard
LIBCARD_REF=main

LIBCARD_REPO is the GitHub owner/repository pair. LIBCARD_REF defaults to main; you can omit it. PUBLIC_URL must be the same HTTPS origin you put in LibCard.

Feedme reads your profile and catalog from libcard.config.yaml. It imports your public name, avatar, links, icons, and supported GitHub metadata. Your Bluesky administrator identity stays the same.

Your links are ready for support.

All links and socials become selectable on Feedme by default, up to 99 plus you. No per-link YAML is required. Hide exceptions in Dashboard → Projects → From LibCard. Set LIBCARD_DEFAULT_SUPPORT=explicit on your Feedme server to keep the older explicit-only behavior.

Optional links back from LibCard

Add a top-level feedme block to your existing libcard.config.yaml. Then add a nested feedme object to each link or social where you want LibCard itself to show a “More of this” action. Merge this example into your own configuration; keep your other links, profile, and theme settings.

feedme:
  enabled: true
  origin: https://support.example.com

links:
  - label: Small, useful tools
    url: https://example.com/tools
    icon: github
    feedme:
      id: tools
      blurb: More time making useful things.
      aspiration: 3000

  - label: My résumé
    url: https://example.com/resume
    # Selectable on Feedme automatically. No card-side tip action yet.

socials:
  - platform: bluesky
    url: https://bsky.app/profile/you.bsky.social
    feedme:
      id: bluesky
      blurb: More of these conversations.

enabled: true turns on LibCard’s tip actions and build-time statistics request. Each card-side tip action needs its own permanent id; an optional blurb explains what more support would make possible.

• Use lowercase letters, digits, and hyphens, starting with a letter or digit. IDs can be up to 64 characters.
• Keep IDs unique across links and socials. Reserve creator and amount; Feedme adds the “Just you” option itself.
• Feedme supports up to 99 source items plus you. Explicit IDs take priority; other links fill the remaining slots automatically. The separate LibCard client still requires a nested object for its own tip actions.
• Keep an ID when renaming a link or moving its destination. For an automatic target, copy its existing ID from Feedme Studio into the YAML before changing its URL. Choosing a different ID starts a new target.

Optional aspirations

aspiration: 3000 means $3,000 USD, in whole dollars. Omit it or use zero for no aspiration. In Feedme Dashboard → Projects → From LibCard, you can hide a target or override its aspiration. Blank inherits the source, zero hides the aspiration, and a positive value replaces it.

Aspirations don’t restrict how you use a tip. LibCard currently displays public pick statistics; it does not display dollar progress toward these goals.

Refresh. Review. Verify.

Commit the YAML to the repository and ref you configured. In Feedme, open Dashboard → Projects → From LibCard → Refresh LibCard, or let the normal background refresh pick it up in roughly 15 minutes.

Check the imported names and targets. A removed source item is archived, and a locally hidden item disappears from the public target list. Import errors keep the last good catalog and show a diagnostic in Studio.

From your Feedme checkout, verify the deployed endpoint:

pnpm check:libcard-origin https://support.example.com

The check verifies a direct response, matching public origin, cache headers, and the public contract at /api/public/libcard. It doesn’t charge anyone or replace the live provider acceptance checks.

Try the links

A target-specific link uses its ID and a count of one:

https://support.example.com/checkout?amount=22.00&tools=1

amount is in dollars. LibCard uses Feedme’s configured default suggestion, rather than a fixed $22. The general “Give to…” action opens /checkout without selections so visitors can choose for themselves.

Build, publish, and let it refresh.

Build and deploy LibCard after Feedme has imported the new IDs. The existing daily LibCard workflow refreshes the public signal on subsequent builds; there is no extra scheduler or browser polling to set up.

pnpm build

Your card’s “More of this” actions are ordinary links. Visitors continue to Feedme to change their picks, amount, frequency, privacy, and note, then review the exact gift before Stripe checkout.

LibCard receives no supporter identities, private notes, or individual payment amounts. Feedme retains the ledger and private recovery.

If something looks wrong