[Flow] Where to store API-Key

David Sporer david.sporer at gmail.com
Mon Mar 16 15:28:48 CET 2015


Yep came to that conclusion also :D

From: carsten at bleicker.de
Date: Sun, 15 Mar 2015 19:56:40 +0100
To: flow at lists.typo3.org
Subject: Re: [Flow] Where to store API-Key

You should not submit the api to the repo ;)
Just add a dummy one.
 
Users of this package have to overwrite this in their context settings.
 
 
Mit sonnigem Gruß
Carsten Bleicker
 
----------------------
 
Carsten Bleicker
Wülfingstraße 1
42477 Radevormwald
 
E-Mail:	carsten at bleicker.de
Web:	www.bleicker.de
Twitter:	@carstenbleicker
Jabber:	cbleicker at jabber.ccc.de
Telefon:	+49 (0)171-2690845
 
> Am 15.03.2015 um 17:28 schrieb David Sporer <david.sporer at gmail.com>:
> 
> Found this example from Bastian Waidelich where the API-Key is just empty in the repository:
> https://github.com/bwaidelich/Wwwision.Neos.MailChimp/blob/master/Configuration/Settings.yaml <https://github.com/bwaidelich/Wwwision.Neos.MailChimp/blob/master/Configuration/Settings.yaml>
> 
> 
>> Am 15.03.2015 um 17:20 schrieb David Sporer <david.sporer at gmail.com>:
>> 
>> Thanks Carsten, but if I commit this to a public repo it would be a bad idea and if I exclude the Settings.yaml then if anyone wants to use the Package would have to find out what settings are needed himself or am I overlooking something?
>> 
>> 
>>> Am 15.03.2015 um 16:29 schrieb Carsten Bleicker <carsten at bleicker.de>:
>>> 
>>> Just put it in Settings
>>> 
>>> Your:
>>> 	Package:
>>> 		Api:
>>> 			Key: 'Foo'
>>> 
>>> in your class inject it by @Flow\InjectConfiguration(package="Your.Package", path="Api.Key")
>>> think this should work with the ne configuration annotation.
>>> 
>>> 
>>> Mit sonnigem Gruß
>>> Carsten Bleicker
>>> 
>>> ----------------------
>>> 
>>> Carsten Bleicker
>>> Wülfingstraße 1
>>> 42477 Radevormwald
>>> 
>>> E-Mail:	carsten at bleicker.de
>>> Web:	www.bleicker.de
>>> Twitter:	@carstenbleicker
>>> Jabber:	cbleicker at jabber.ccc.de
>>> Telefon:	+49 (0)171-2690845
>>> 
>>>> Am 15.03.2015 um 16:20 schrieb David Sporer <david.sporer at gmail.com>:
>>>> 
>>>> Hi,
>>>> 
>>>> I’m currently working on a package I thought might be worth sharing (Integration of the Newsletter2Go API).
>>>> But for the API-Calls to their API I have to provide an API Key.
>>>> If I create a plain old PHP class I’d pass the API-Key to the constructor so everyone can save their own API key in their own projects and pass them to the class.
>>>> But how would I do this in Flow?
>>>> 
>>>> Regards,
>>>> David
>>>> _______________________________________________
>>>> Flow mailing list
>>>> Flow at lists.typo3.org
>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>>> 
>>> _______________________________________________
>>> Flow mailing list
>>> Flow at lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>> 
>> _______________________________________________
>> Flow mailing list
>> Flow at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
> 
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
 

_______________________________________________
Flow mailing list
Flow at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/flow 		 	   		  


More information about the Flow mailing list