Closed tripodsan closed 2 years ago
Wouldn't it be possible to do this within the existing helix-pipeline
code base?
Wouldn't it be possible to do this within the existing
helix-pipeline
code base?
What would be the benefit? There's just too much legacy code and dependencies. It's IMO easier to make a clean cut and start with a new repo.
It's IMO easier to make a clean cut and start with a new repo.
that was my idea. and if, in the very unlikely event that we need to re-activate the old helix2 serverside rendering, not too much is lost :-)
@trieloff would you be so kind to add the social image? https://github.com/adobe/helix-html-pipeline/settings
Create a new library repository with the name
helix-html-pipeline
.Helix HTML Pipeline
This package contains the common code for
helix-pipeline-service
andhelix-cloudflare-pipeline
for rendering the html response for helix3. it has the following design goals: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