Skip to content
This repository has been archived by the owner on Mar 1, 2023. It is now read-only.

Support for building Postfacto using Buildpacks. #404

Open
kulhadia opened this issue Sep 9, 2021 · 2 comments
Open

Support for building Postfacto using Buildpacks. #404

kulhadia opened this issue Sep 9, 2021 · 2 comments

Comments

@kulhadia
Copy link

kulhadia commented Sep 9, 2021

Hello,
My team was trying to build the postfacto app using Buildpacks and currently, we are not successful in doing so.
So would like to know if there are considerations to support the use of Buildpacks for building the postfacto app in the future.

@textbook
Copy link
Contributor

textbook commented Sep 9, 2021

I'm not sure what specifically you've been trying, but Postfacto already deploys to Cloud Foundry/Tanzu Application Service using the CF Ruby buildpack:
https://github.com/pivotal/postfacto/blob/db61713a38d6a8a945840e0965c88cbaee02510b/deployment/tas/config/manifest.yml#L5-L6
so it should be possible. Are there particular issues you've run into that suggest that something needs to be changed?

@kulhadia
Copy link
Author

We are trying to build it with Paketo Buildpack. We are using the following command.

pack -v build --builder paketobuildpacks/builder:full -e DATABASE_URL="postgres://test:test@test" -e SECRET_KEY_BASE=random postfacto:latest

we have checked with Paketo slack community regarding the same issue. here

The main issue is that the node engine is not present during runtime (due to the uglifier dependency). To our understanding, this should not be necessary as the assets are already minified.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants