Questions around the TYPO3 integration and plugins as well as Flow and NeosCMS
Forum rules: Always add your TYPO3/Flow, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
#2268 by andreas.allacher
22 Dec 2015, 19:15
I will probably experiment during the upcoming weekend/holidays so here some last questions:

So I best checkout https://github.com/aimeos/aimeos-typo3 and then do
COMPOSER=composer.aimeos.json composer update

Btw. wouldn't it make sense to include a composer.aimeos.lock file to ensure the same aimeos core is installed when doing a composer install?

One other thing in the composer.aimeos.json there is:
"vendor-dir": "Resources/Libraries"

If the libriaries don't contain any public images or similar I think you should place them in "Resources/Private/Libraries" as Resources/Private have htaccess denied in the default TYPO3 htaccess which is not the case for Resources/Libraries.

EDIT:
If I install the EXT using a own composer.json do I then have to execute COMPOSER=composer.aimeos.json composer update / install manually, e.g. adding scripts to the composer.json or is it done automatically with a composer installer?
#2270 by aimeos
23 Dec 2015, 10:59
andreas.allacher wrote:So I best checkout https://github.com/aimeos/aimeos-typo3 and then do
COMPOSER=composer.aimeos.json composer update


Yes, that's correct. It's like described here: https://aimeos.org/docs/TYPO3/Download_Aimeos#Latest_code

andreas.allacher wrote:Btw. wouldn't it make sense to include a composer.aimeos.lock file to ensure the same aimeos core is installed when doing a composer install?


We've tested a lot if we should use a composer.lock file or not. Lastly, we've decided to remove it because it's not necessary, make more work and can even do more harm than it helps.

andreas.allacher wrote:If the libriaries don't contain any public images or similar I think you should place them in "Resources/Private/Libraries" as Resources/Private have htaccess denied in the default TYPO3 htaccess which is not the case for Resources/Libraries.


It contains the CSS files and images of the admin interface so it's not that easy to move it to a protected directory.

andreas.allacher wrote:If I install the EXT using a own composer.json do I then have to execute COMPOSER=composer.aimeos.json composer update / install manually, e.g. adding scripts to the composer.json or is it done automatically with a composer installer?


You still have to do it manually. We haven't experimented much with TYPO3 composer installs up to now as in 6.2 the packagist repository wasn't available. This rendered it pretty useless for Aimeos. If you are able to get it to work now. we would be glad to merge any required changes :-)
#2271 by andreas.allacher
23 Dec 2015, 15:03
Regarding composer.lock:
You are right in regards that as long as the version constraint is restrictive enough it really shouldn't matter and might require unnecessary composer.lock Updates.

Regarding composer autoinstall:
I think in 7.6 it would be possible to add it to the normal composer.json actually as 7.6 loads vendor libraries correctly with composer installations and uses ext_emconf.php for Extension dependencies in extension manager.

However, I would have to check if it is possible to install the library into typo3conf/ext/... although would it be necessary to have it there?
#2273 by aimeos
23 Dec 2015, 16:41
andreas.allacher wrote:Regarding composer autoinstall:
I think in 7.6 it would be possible to add it to the normal composer.json actually as 7.6 loads vendor libraries correctly with composer installations and uses ext_emconf.php for Extension dependencies in extension manager.

However, I would have to check if it is possible to install the library into typo3conf/ext/... although would it be necessary to have it there?


It's not really necessary because the integrations into Laravel/Symfony/Flow don't expect it to be there as well. There's a hard coded require() for the composer autoloader in the Base class which could be removed and the CSS files and images could be copied to the ./Resources/Public/ directory like the framework integrations do.
#2274 by andreas.allacher
23 Dec 2015, 16:48
I will check. How would you do the copy to Resources/Public ?

However, in case of TYPO3 being installed without composer the library would have to be included manually but that could be done when packaging it for TYPO3 TER repository and e.g. include the autoload if COMPOSER_MODE (I think the constant is called that way) is not active or not set.
#2275 by aimeos
23 Dec 2015, 21:37
andreas.allacher wrote:I will check. How would you do the copy to Resources/Public ?


In Flow/Laravel/Symfony it's done in the composer.json file as post-install/post-update script. In TYPO3 there was a phing target a while ago that did the same.
#2404 by aimeos
27 Jan 2016, 17:03
andreas.allacher wrote:As I didn't find the time to start prior to this week with my implementation, I wanted to ask if I still should use the dev-master or has the necessary update already been released?


Yes, that should be your preferred option until next week. Then, the new Aimeos TYPO3 extension based on dev-master will be released.