devnix

As @doclucas said, this is where the Prestashop compatibility and a smooth and easy migration system between shops are essential components for TB to live.

Sorry for the late answer @hubbobubbo! I'm not actively maintaining it, but if you have any issue or doubt I will be more than happy to fix and document anything you need. I'm currentry trying to make a module framework to help smoothing sharp things and incompatibilities between Prestashop versions (1.5, 1.6, 1.7). One of the base ideas of the framework is to give a preconfigured set of different Prestashop installations with different PHP versions, and I would absolutely love to support Thirtybees too. To make it possible, I think we should fork the way Prestashop is generating the Docker images, and maintain official Thirtybees Docker. If you need something about me you can contact me trough my Github account.

@mdekker True! I also had to modify the length of the password field in the database if I'm not wrong! Is the repo of the migration module available anywhere? I would love to help where I can :D We have several shops at our work that I can replicate into several environments to test/improve the module, find special cases... :D

@rabbit80 I've been too into this situation. I've ended restarting the admin's password via phpmyadmin... There are also a couple of problems. For example, the articles permalinks system has been modified (for better :dancer_tone1: ), but you would have to save every existing article to generate the permalinks. As I understand, this kind of little issues will be automatized in a migration tool. About the login... I don't know how TB will handle it without forcing to restart the password to every users. I'm following this thread closely :)

Wouldn't be AWESOME to be able of running the installer without inserting demo data? :smile:

I've initially configured the docker-compose with a nginx image instead of an apache one, so the friendly urls will not work as expected. I'm going to bake two php-apache containers to images for faster bootstrappìng. One with opcache optimized for testing in a more speed friendly environment, and a second one without opcache, and xdebug enabled.

Glad to hear you got it to work! Could you please describe what was your problem to help other people in the future with a similar issue?

Not sure if would be wise to suppress a warning... Maybe I just have to configure my php.ini properly

@roband7 I agree with you, although I'm pretty sure that there exists bugs and needed features way more important than this

@mdekker Yyyyyyyyyyyup :/ So, the fix would be to configure PHP, and it is not related with TB codebase, right?

Hi! I'm starting to work using xdebug and enabling dev mode, and I saw this in the first page of the installer; I don't know if you are aware about it :) Seems like it is something related to tempnam() in PHP 7.1 specifically. Cheers!

Permissions? I would check the PHP error log

I'm ending the weekend, and I wanted to give a try at my job for my boss of Thirty Bees (and I would love to clone a client's production website on a local machine and migrate to TB). For that purpose, I've done a custom php-fpm 7 container with all the dependencies required by TB, and a memcached server to try the new cache (as this could be the main reason for me to migrate from PS to TB). Here you have the Github repo, I'm willing to maintain it actively. If you find it good enough we could clone the repo to the Thirty Bees Github organization. https://github.com/DevNIX/thirtybees-docker-compose For future work I would look into: - Build the php-fpm configuration as an image (to speed up the docker-compose up -dcommand), add more PHP versions) - Provide an Apache image as an alternative to Nginx - Provide more useful images, for example Redis - Run the PHP image with development features (like xdebug) - Give the capacity to auto-install Thirty Bees, update configuration parameters through env variables... just like the Prestashop's docker-compose (I would need a hand with that one :smiley:) You can give me your feedback in the repository, as a new issue. I would love to hear your opinion here, too! Happy deploying, and happy developing!