Create a new service repository with the name helix-nui-poc-worker.
From what I understand, I need first the repo, then I can run through the checklist, so here we are!
The goal is to start a POC of a Nui worker running as serverless function on AWS. The requested repo will hold the part deployed to AWS Lambda for that POC.
Stuff you can do yourself
[ ] run npm init @adobe/helix-library or npm init @adobe/helix-service
[ ] Add topics to the repository, at least helix
[ ] Add the group "Project Helix Admins" with Admin permissions to the list of collaborators
[ ] Add the group "Project Helix Developers" with Write permissions to the list of collaborators (Project Helix Guests will be taken care of automatically)
[ ] Uncomment and adjust the helix-post-deploy/monitoring command in .circleci/config.yaml: decide if your service falls under Development, Publishing or Delivery. (note: failures in the latter two categories will ping on-call engineers on weekends!) See https://status.project-helix.io for reference.
[ ] Add a CIRCLECI_TOKEN to the repository secrets.
Stuff you need an Adobe Org Admin for
[ ] Enable Renovatebot (this is optional for now, as we're in the POC phase)
Create a new service repository with the name
helix-nui-poc-worker
. From what I understand, I need first the repo, then I can run through the checklist, so here we are!The goal is to start a POC of a Nui worker running as serverless function on AWS. The requested repo will hold the part deployed to AWS Lambda for that POC.
Stuff you can do yourself
npm init @adobe/helix-library
ornpm init @adobe/helix-service
helix
for services
helix-post-deploy/monitoring
command in.circleci/config.yaml
: decide if your service falls under Development, Publishing or Delivery. (note: failures in the latter two categories will ping on-call engineers on weekends!) See https://status.project-helix.io for reference.CIRCLECI_TOKEN
to the repository secrets.Stuff you need an Adobe Org Admin for
for libraries
ADOBE_BOT_NPM_TOKEN
org secret