Closed fnagel closed 9 years ago
Totally in a commit/release frenzy here ^^
Implementation sort of similar to https://github.com/NamelessCoder/typo3-repository-gizzle/blob/master/src/GizzlePlugins/ExtensionRepositoryReleasePlugin.php#L47 but builds on an option rather than some third-party user input.
Thanks a lot! Seems to work as expected -- at least the folder is created correctly now.
TER deploy itself fails at the moment as I'm running into an odd issue, see https://github.com/NamelessCoder/typo3-repository-client/issues/1
I like the idea of setting the extension key in the URL -- that way its not needed to add an specific setting yml for each extension just because the repo name. What about a combination of both options?
Works like expected -- expect that my TER upload fails due to that dependency issues.
Thanks again! Do you have a amazon wishlist? It seems you need some more fine metal music :-D
I wouldn't like receiving SOAP requests with dependency info either, poor TER ^^
I sure do have a wish list, there's a little bit of everything on there: http://www.amazon.co.uk/registry/wishlist/4DBU03X4O79U - thanks! ;)
Did you receive a package? Amazon claims it "will be delivered soon" for more than a month now...
I sure did - thanks for the metal! Received almost a month ago and enjoyed several times since then ;)
Running into this issue:
I've seen there is a option in typo3-repository-gizzle to pass the extension key as URL path but this seems not possible when using fluidtypo3-gizzle, right?
Any other way to change extension key per repository?