-
Notifications
You must be signed in to change notification settings - Fork 166
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
support an optional service to build the image instance in the Controller #21
Comments
You can use your own controller. It is possible to set it in service container:
The controller can look like this:
|
sure you can .. but it would be better to refactor the existing controller to be more extensible |
@avalanche123: is there an ETA for this? IIRC you said you would have a go at this, if not i will try to find time to get on this during this week. |
FYI .. i am working on a rather large refactoring that includes this feature among several others. |
closed in favor of #25 |
we dont store our images in the file system, instead we store it in a content repository. it would help us therefore if the controller could be refactored a bit to make it possible to optionally define a service that creates the imagine instance, rather than the hardcoded file system approach.
The text was updated successfully, but these errors were encountered: