Skip to content
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

Open
stof opened this issue Dec 5, 2012 · 4 comments
Open

Use a config file to configure the buildpack #8

stof opened this issue Dec 5, 2012 · 4 comments

Comments

@stof
Copy link

stof commented Dec 5, 2012

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)

@Swop
Copy link
Owner

Swop commented Dec 5, 2012

It's something which is planned.

For now, we use our own bucket to easily test the new code.
Env vars will be used once the buildpack is correctly working.

@stof
Copy link
Author

stof commented Dec 5, 2012

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.
Maybe we could use the env variable when available, then fallback to a value coming from a config file (if the config file exists and provides the value) and finally fallback to the default set in the buildpack itself.

@stof
Copy link
Author

stof commented Jul 25, 2013

@Swop is there any news about this ? It looks like making the buildpack configurable has not been implemented yet

@Swop
Copy link
Owner

Swop commented Jul 25, 2013

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.
However, I do not consider to give up on this project, given that I don't think there is still a convincing alternative buildpack to build a custom Symfony2 stack in Heroku.

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 :-)

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

No branches or pull requests

2 participants