Tsarin yana cikin sashen 5 na docs/architecture/23-ops.md. Vercel yana gudanar
da sashen yanar gizo kawai. Duk sauran abubuwa suna gudana a uwar garke na rakiya
da kake sarrafawa; ba za a iya barin wannan uwar garken ba.
Matsayi a wannan siga
An shirya saituna (apps/web/vercel.json, saitin Nitro na vercel da gwaje-gwajen
farawa). Vercel yana buƙatar ma’ajiyar fayil da aka raba (QUIRE_STORAGE_DRIVER=s3
ko azure), na’urar ainihin-lokaci da ke aiki tsakanin misalan aiki
(QUIRE_REALTIME_DRIVER=sse ko centrifugo) da mai aika imel ta HTTP. Idan ba su
nan, sashen yanar gizo zai ƙi farawa, log ɗinsa kuma zai lissafa saitin da ya ɓace.
Uwar garke na rakiya: Fly, Railway, ECS, ko naka Docker mai docker/compose.yaml
Postgres
Na waje, bayan mai tara haɗin ma’amala: Neon, Supabase ko RDS mai PgBouncer
Fayiloli
S3 ko R2. Babu faifai mai ɗorewa
Ayyukan baya
Ana sa su cikin pg-boss a cikin ma’amalar buƙata, mai aiki na rakiya ne ke aiwatar da su. Idan mai aikin rakiya yana da QUIRE_QUEUE_DRIVER=vercel, ayyukan sauƙi (sanarwa mara jeri da isar da webhook) suna tafiya ta Vercel Queues (VERCEL_QUEUE_REGION, VERCEL_QUEUE_TOKEN), saboda haka ba a duba Postgres da aka tara domin su
Ayyukan da ake maimaitawa
Mai tsara aikin rakiya. Babu hanyar Vercel Cron, domin cron mai yin aiki a cikin function zai ƙare saboda iyakar lokaci
Bibiya
OpenTelemetry zuwa mai tattarawarka, OTEL_EXPORTER_OTLP_ENDPOINT
Abin da wannan manufa ba za ta iya yi ba
Sashen yanar gizo yana duba waɗannan yayin farawa kuma yana ƙi tare da bayyana
kowace matsala, maimakon a gano daga baya lokacin da imel bai fita ba:
Babu SMTP. Vercel yana toshe SMTP mai fita. Saita QUIRE_EMAIL_PROVIDER_CONFIG
zuwa mai samarwa ta HTTP (Postmark, SES, Mailgun, SendGrid ko Resend).
Ana ƙin QUIRE_SMTP_URL.
Babu faifan gida. Ana ƙin QUIRE_STORAGE_DRIVER=local.
Babu ƙwaƙwalwa ta bai ɗaya tsakanin kira. Ana ƙin QUIRE_REALTIME_DRIVER=inprocess.
An ƙayyade lokacin ayyukan server-sent events, abokin ciniki kuma yana sake haɗawa
da cursor, don haka babu taron da ya ɓace, amma ganin masu halarta ba ya samuwa.
An iyakance ma’ajiyar bayanai ta ƙungiya da aka keɓe zuwa kusan guda takwas,
domin kowacce tana ƙara wani tafkin haɗi a yanayin da ba zai iya raba tafkuna ba.
Tura sigar
Ƙirƙiri aikin Vercel daga ma’ajiyar lamba da Root Directoryapps/web. apps/web/vercel.json yana saita umarnin girkawa da gini
(NITRO_PRESET=vercel) kuma yana aika /sw.js ba tare da adanawa ba.
Saita sauye-sauyen yanayi. Daga docker/.env.example, aƙalla:
QUIRE_DEPLOY_TARGET=vercel, QUIRE_APP_ORIGIN, QUIRE_CONTENT_ORIGIN,
QUIRE_PLATFORM_DOMAINS, QUIRE_SECRET_KEY, QUIRE_MASTER_KEY,
DATABASE_URL (adireshin mai tara haɗi), QUIRE_REPORT_DATABASE_URL,
QUIRE_AUDIT_DATABASE_URL, QUIRE_DATABASE_ID,
QUIRE_EMAIL_PROVIDER_CONFIG, QUIRE_MAIL_FROM, saitunan ajiya,
QUIRE_COLLAB_URL da QUIRE_COLLAB_SIGNING_KEY masu nuni ga hidimar
collab a uwar garken rakiya. QUIRE_REPORT_DATABASE_URL na ainihin
ma’ajiyar da DATABASE_URL ya nuna ne. Ga kowace ma’ajiya ta daban da aka
yi rajista, ƙara nata adireshin haɗin quire_report a muhallin yanar gizo da
na mai aiki, sannan yi rajistar sunan sauyin yanayi a matsayin env:NAME a
console na dandamali. Nazari ba ya aiki idan adireshin rahoton wannan ma’ajiya
ya ɓace.
A uwar garken rakiya, gudanar da docker/compose.yaml ba tare da sabis na
web ba, da docker/.env iri ɗaya:
Ana gudanar da ƙaura a can kafin a ɗaga kowace tura ta Vercel.
Tura sigar. Idan an ƙi saituna, log ɗin function yana farawa da
“The web tier did not start on vercel” kuma yana lissafa saitin da za a canza.
Sabuntawa
Da farko yi ƙaura daga uwar garken rakiya, sannan ɗaga sabon turawar Vercel,
daga baya sabunta masu aikin rakiya: tsarin yana cikin jagorar sabuntawa.
Mayar da Vercel nan take zuwa baya mayar da lamba ce kuma kullum yana da lafiya
a cikin siga ɗaya.