{"_id":"@algea_care/pdf-service","_rev":"17-85757378ea43eda2f7c0a30c93c1867d","name":"@algea_care/pdf-service","dist-tags":{"latest":"1.0.0"},"versions":{"1.0.0":{"name":"@algea_care/pdf-service","version":"1.0.0","author":{"name":"Bloomwell GmbH"},"license":"Private","_id":"@algea_care/pdf-service@1.0.0","maintainers":[{"name":"algeacare","email":"gareth.fuller@algeacare.com"},{"name":"juce93","email":"julien.wiedner@algeacare.com"},{"name":"medhabloom","email":"Mohamed.Hamza@bloomwell.eu"},{"name":"puskuruk","email":"tamayeseruysal@gmail.com"},{"name":"mainulshuvro","email":"mainul.shuvro@bloomwell.de"},{"name":"lelouchb","email":"ashusingh15673@gmail.com"},{"name":"sirjiggles","email":"gareth126@gmail.com"},{"name":"ivan.prokopenko","email":"prokopenko.co@gmail.com"},{"name":"yyalim","email":"yusufyalim@gmail.com"},{"name":"aruan.carrara.bloomwell","email":"aruan.carrara@bloomwell.de"}],"homepage":"https://github.com/AlgeaCare/pdf-service#readme","bugs":{"url":"https://github.com/AlgeaCare/pdf-service/issues"},"dist":{"shasum":"997b577ea2cc9ecf2e515b73f3288cabf2798f39","tarball":"https://registry.npmjs.org/@algea_care/pdf-service/-/pdf-service-1.0.0.tgz","fileCount":296,"integrity":"sha512-qiqgBfjbiJh1qqk3Ug0WQbmyy7MNHM7JO3JBsbXZ4kJ8WlimdKIQb7eB94mKR9VmFgRpamx03fa3wnOPmj8kVQ==","signatures":[{"sig":"MEUCIDmcZOo+yZGyyKAq+IYykXboQXskE5lab8aY6x/+t3OcAiEA8kiH4kwr+PK5+14JPTwajibTecorI/GSlUx0KE0sqRY=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":7524223},"main":"index.js","gitHead":"00d952e23bbe4f64caeee58a3e5944e75a13b2b5","scripts":{"e2e":"cd packages/e2e && npm run start","lint":"lerna run lint","test":"lerna run test","build":"npx lerna run --ignore @algeacare/payment-service-infrastructure build","clean":"lerna clean --yes && npm run remove-node-modules && npm cache clean --force","deploy":"cd packages/backend && npm run package && cd ../infrastructure && npm run deploy:approve","bootstrap":"lerna bootstrap","deploy:backend":"cd packages/infrastructure && npm run deploy:backend","remove-node-modules":"rm -rf packages/backend/node_modules packages/infrastructure/node_modules packages/pdf/node_modules packages/ui/node_modules packages/api-types/node_modules"},"_npmUser":{"name":"lelouchb","email":"ashusingh15673@gmail.com"},"repository":{"url":"git+https://github.com/AlgeaCare/pdf-service.git","type":"git"},"_npmVersion":"11.3.0","description":"The PDF service project, this project just serves PDF's does nothing else with em","directories":{},"_nodeVersion":"22.14.0","_hasShrinkwrap":false,"devDependencies":{"lerna":"^6.0.0"},"_npmOperationalInternal":{"tmp":"tmp/pdf-service_1.0.0_1759139050830_0.009970030633860372","host":"s3://npm-registry-packages-npm-production"}}},"time":{"created":"2025-09-29T09:44:10.707Z","modified":"2026-09-23T13:30:50.407Z","1.0.0":"2025-09-29T09:44:11.068Z"},"bugs":{"url":"https://github.com/AlgeaCare/pdf-service/issues"},"author":{"name":"Bloomwell GmbH"},"license":"Private","homepage":"https://github.com/AlgeaCare/pdf-service#readme","repository":{"url":"git+https://github.com/AlgeaCare/pdf-service.git","type":"git"},"description":"The PDF service project, this project just serves PDF's does nothing else with em","maintainers":[{"email":"gareth.fuller@algeacare.com","name":"algeacare"},{"email":"julien.wiedner@algeacare.com","name":"juce93"},{"email":"Mohamed.Hamza@bloomwell.eu","name":"medhabloom"},{"email":"thomas.gerdes@bloomwell.de","name":"thommygee49"},{"email":"marc.ackermann@bloomwell.de","name":"marc_ac_bw"},{"email":"mainul.shuvro@bloomwell.de","name":"mainulshuvro"},{"email":"Volodymyr.Sabaiev.ext@bloomwell.de","name":"ede-vsabaev"},{"email":"Manuel.Ramirez@Bloomwell.de","name":"bloomwell-manu"},{"email":"volodymyr.Shabat.ext@bloomwell.de","name":"volodymyr.shabat.ext"},{"email":"donn.williams@bloomwell.de","name":"donnwilliams"},{"email":"Soumya.Sobha@bloomwell.de","name":"soumyabhasisobha"},{"email":"Majid.Qureshi@bloomwell.de","name":"majid.bloomwell"},{"email":"s.nagy@ghostchef.co","name":"nodschi"},{"email":"ashusingh15673@gmail.com","name":"lelouchb"},{"email":"gareth126@gmail.com","name":"sirjiggles"},{"email":"prokopenko.co@gmail.com","name":"ivan.prokopenko"},{"email":"yusufyalim@gmail.com","name":"yyalim"},{"email":"aruan.carrara@bloomwell.de","name":"aruan.carrara.bloomwell"},{"email":"Yaroslav.Plaksii.ext@bloomwell.de","name":"yaroslav_plaksii"}],"readme":"# PDF Service\n\nThis is the PDF service, it is an ec2 container that just serves PDF's with an express server. You can pass a callback to call when then pdf is done. This is because PDF's can take a while to generate.\n\nTo use the service you need to pass a token that we check to make sure you have access to 'create' PDF's\n\n## System requirements\n - Node\n - AWS CLI\n - Terraform CLI\n\n## Getting started 🏁\n\nBefore starting the project, check that an NPM token is set in the machine. Please make sure you are part of the company npm team, this way you will have access to the private packages.\n\nTo get started run these commands:\n\n\n- `npm i` install lerna and root deps\n- `npm install --global cdktf-cli@latest` make sure you have cdktf (for infra as code) installed\n- `npm run bootstrap` to install all the packages in all the folders.\n- ONCE per Stack `npm run deploy:backend` to setup the bucket and table that holds the terraform state BEFORE `deploy`\n- `npm run deploy` build and package the backend, then deploy the infra (auto confirm) with the new backend source code\n\nfor the first deploy of your stack you also need to be signed into NPM with access, check out the packages section of the readme for the why.\n\nfor an example of what sort of env vars you need, have a look at the git actions for staging and prod. and check the env.example files to see where to put them\n\nOther commands you can do from root\n\n- `npm run lint` lint all the packages in packages folder\n\n## Structure\n\nThis repo is structured using lerna which is a package for managing packages. each folder in the packages folder can be thought of as a single npm package.\n\nAs such, each package is like a separate app that needs it's own env file and so on. There is an env.example file in each package with details on each config setting inside each package.\n\n### Backend\n\n@TODO Murat: you can read more about it [here](./packages/backend/README.md)\n\n### Infrastructure 🏘\n\nThe infra package is all about the aws infra that is deployed using [cdktf](https://developer.hashicorp.com/terraform/cdktf)\n\nYou can read about it [here](./packages/infrastructure/README.md)\n\n## Configuration 🔧\n\nEach package contains a .env.example file giving instruction to set up the packages as they are needed. it is not ideal but we will do proper secret management and config generation soon. we just want to test the MVP right now. and when I say we will, I really mean it!\n\nOne important thing to remember that catches people out a fair bit is that the config vars in the backend folder are only used when running the test scripts that run on lambda local calls. The real env vars you will use for your stack that get set on the backend lambdas are the ones in the INFRA package, as this is the one that actually makes the lambdas, so it is the one that will set up the env config for the lambdas.\n\n## Deployments 🚀\n\nFor Staging deployments merge dev to main.\n\nDeployments are done automatically via git actions, there is a workflow that will run tests first that run on all branches\n\nfor staging deployments simply merge the branch to main, terraform will deploy the rest!\nfor production deployments, make a new tag for the repo, terraform will deploy it.\n\nthere are two git actions for these `deploy_prod` & `deploy_staging` both should have the env vars they need in git action secrets on the repo.\n","readmeFilename":"README.md"}