-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use a config file to configure the buildpack #8
Comments
It's something which is planned. For now, we use our own bucket to easily test the new code. |
I think some stuff should be able to be configured through a file shipped in the repo instead of relying on env variable for everything. For instance, we are deploying our app twice: the staging server and the prod server. Some stuff definitely deserve to be in the env variables as it may change, but some other don't make sense to change between deployments (PHP version...). for these, it would be easier to have a versionned file than havig to update the env variables on both heroku apps each time. |
@Swop is there any news about this ? It looks like making the buildpack configurable has not been implemented yet |
I did not have a lot of time to move forward on this project. Furthermore, as my company decided to pass on another hosting platform, I wasn't able to dedicate some of my work time on it. But after quite a lot of reflexion about the buildpack design, I found that it will be more clever to develop an event-driven & framework-agnostic buildpack and extends this base to build Sf2 apps. Such a "middleware" buildpack could also be use for other framework or use-case. So it's quite a huge and exiting side project, but it's currently only developed on my free time (which is quite ridiculous unfortunately :-S) But thanks for your interest :-) |
Currently, any change to the buildpack would require maintaining a fork. A common use case would be fetching the deps from a different bucket to use a different PHP version (either newer or with different extensions)
The text was updated successfully, but these errors were encountered: