m13o

FROM ubuntu:latest
RUN apt update -y && apt install -y certbot

mkdir letsencrypt

docker build -t certbot ./
docker run -it -v "./letsencrypt:/etc/letsencrypt" --name certbot certbot:latest /bin/bash

# ここからはコンテナの中の操作
docker:/# certbot --manual --preferred-challenges dns certonly -d customfeed.example.com

# メールアドレスの入力を求められる
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Enter email address (used for urgent renewal and security notices)
(Enter 'c' to cancel): ${YOUR_EMAIL_ADDRESS}

# 規約の同意等
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf. You must
agree in order to register with the ACME server. Do you agree?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: y

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing, once your first certificate is successfully issued, to
share your email address with the Electronic Frontier Foundation, a founding
partner of the Let's Encrypt project and the non-profit organization that
develops Certbot? We'd like to send you email about our work encrypting the web,
EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: y
Account registered.
Requesting a certificate for customfeed.example.com

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please deploy a DNS TXT record under the name:

_acme-challenge.customfeed.example.com.

with the following value:

${ACME_CHALLENGE_TEXT} # 長ったらしい英数字のテキスト

Before continuing, verify the TXT record has been deployed. Depending on the DNS
provider, this may take some time, from a few seconds to multiple minutes. You can
check if it has finished deploying with aid of online tools, such as the Google
Admin Toolbox: https://toolbox.googleapps.com/apps/dig/#TXT/_acme-challenge.coustomfeed.example.com.
Look for one or more bolded line(s) below the line ';ANSWER'. It should show the
value(s) you've just added.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/customfeed.example.com/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/customfeed.example.com/privkey.pem

git clone [email protected]:bluesky-social/feed-generator.git

// max 15 chars
- export const shortname = 'whats-alf'
+ export const shortname = 'bird'

export const handler = async (ctx: AppContext, params: QueryParams) => {

- import * as whatsAlf from './whats-alf'
+ import * as bird from './bird'

type AlgoHandler = (ctx: AppContext, params: QueryParams) => Promise<AlgoOutput>

const algos: Record<string, AlgoHandler> = {
-   [whatsAlf.shortname]: whatsAlf.handler,
+   [bird.shortname]: bird.handler,
}

const postsToCreate = ops.posts.creates
      .filter((create) => {
-         // only alf-related posts
-         return create.record.text.toLowerCase().includes('alf')
+        return create.record.text.toLowerCase().includes('bird')
      })
      .map((create) => {

FROM node:18-alpine
WORKDIR /build
COPY ./feed-generator /build

RUN npm install
RUN npm run build


FROM node:18-alpine
ENV NODE_ENV production
WORKDIR /app
RUN apk add --no-cache tini
COPY --chown=node:node --from=0 /build/dist /app
COPY --chown=node:node --from=0 /build/package.json /app/package.json
COPY --chown=node:node --from=0 /build/.env /app/.env

RUN npm install --omit=dev

USER node
ENTRYPOINT ["/sbin/tini", "--"]
CMD ["node", "/app/index.js"]

location /xrpc {
    proxy_pass http://feed-generator:3000/xrpc;

    #CORS
    add_header Access-Control-Allow-Origin "*";
    add_header Access-Control-Allow-Methods "POST, GET, OPTIONS";
    add_header Access-Control-Allow-Headers "Origin, Authorization, Accept";
    add_header Access-Control-Allow-Credentials true;
}

version: "3.8"

services:
  feed-generator:
    container_name: feed-generator
    build:
      context: ./
      dockerfile: ./Dockerfile
    volumes:
      - ./db:/db
    environment:
      - VIRTUAL_HOST=customfeed.example.com
      - VIRTUAL_PORT=3000
    networks:
      - default
  nginx-proxy:
    container_name: nginx-proxy
    image: jwilder/nginx-proxy:alpine
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - ./vhost.d:/etc/nginx/vhost.d:ro
      - ./certs:/etc/nginx/certs:ro
    restart: always
    environment:
      - ENABLE_IPV6=true
      - TZ=Asia/Tokyo
    networks:
      - default
    ports:
      - 80:80
      - 443:443

networks:
  default:

docker-compose up -d

// YOUR bluesky handle
// Ex: user.bsky.social
- const handle = ''
+ const handle = {Blueskyのユーザー名}

// YOUR bluesky password, or preferably an App Password (found in your client settings)
// Ex: abcd-1234-efgh-5678
- const password = ''
+ const password = {AppPassword}

// A short name for the record that will show in urls
// Lowercase with no spaces.
// Ex: whats-hot
- const recordName = ''
+ const recordName = 'bird' // algos/bird.tsのshortnameと同じ値にする必要がある

// A display name for your feed
// Ex: What's Hot
- const displayName = ''
+ const displayName = 'Bird' // フィードの表示名

// (Optional) A description of your feed
// Ex: Top trending content from the whole network
- const description = ''
+ const description = 'Posts include bird' // フィードの説明

// (Optional) The path to an image to be used as your feed's avatar
// Ex: ~/path/to/avatar.jpeg
const avatar: string = ''

npm install
npm run publishFeed

FROM node:18-alpine
WORKDIR /publish
COPY feed-generator /publish

RUN npm install

CMD ["npm", "run", "publishFeed"]

docker build -t publish_feed -f Dockerfile .
docker run publish_feed

All done 🎉