Day-to-day usage of this fork

[erikhansen]

@drpayyne

I’ve read the issues you’ve opened in the Warden Github about using Warden on ARM, and I’ve looked at this fork.

I’m curious what your experience has been using this fork on an ARM Mac? What issues have you encountered? What PHP version(s) are you using?

Do you know how many others are using your warden-multi-arch fork?

I ordered an M1X MacBook Pro and it’s coming in late November, and I’m hoping I can use Warden on it without too many issues.

[drpayyne]

Hi @erikhansen, thank you for creating this discussion! To summarize:

• I use the version 0.13.0 tagged in this repo on a daily basis for my client projects. So yes, it's very stable for daily usage including xDebug 3. Catches? Only certain versions of each service is available. Only 7.4 in PHP for example. You can check the README in https://github.com/drpayyne/warden-multi-arch/tree/0.13.0 to view the available versions.
• Moving to debian allows us to be dependent on the official PHP Docker images which has every version needed in multiple Debian flavours, and mainly actively maintained multi-arch support. There is also a project recognized by the official PHP repo - install-php-extensions which allows us to effortlessly manage and install PHP extensions. Both of these are actively maintained and well supported for all versions and architectures.
• I have successfully rebuilt the PHP images using Debian instead of CentOS for versions 7.3 and 7.4. BUT, the Mutagen sync is failing on startup which I'm investigating at the moment. Anyone has any idea on what's causing this? :/ Getting this to work will allow projects running on PHP 7.3 to be developed.

$ warden env up

Creating network "m236_default" with the default driver
Creating volume "m236_bashhistory" with default driver
Creating volume "m236_sshdirectory" with default driver
Creating volume "m236_dbdata" with default driver
Creating volume "m236_esdata" with default driver
Creating volume "m236_appdata" with default driver
Creating m236_elasticsearch_1 ... done
Creating m236_db_1            ... done
Creating m236_php-fpm_1       ... done
Creating m236_nginx_1         ... done
Creating m236_php-debug_1     ... done
Connecting traefik to m236_default network
Connecting tunnel to m236_default network
Connecting mailhog to m236_default network
Starting m236_db_1            ... done
Starting m236_elasticsearch_1 ... done
Recreating m236_php-fpm_1     ... done
Recreating m236_nginx_1       ... done
Recreating m236_php-debug_1   ... done
Installing agent...
Error: unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to install agent: unable to invoke agent installation: exit status 1
ERROR: Command `mutagen sync create -c "${MUTAGEN_SYNC_FILE}" --label "warden-sync=${WARDEN_ENV_NAME}" --ignore "${WARDEN_SYNC_IGNORE:-}" "${WARDEN_ENV_PATH}${WARDEN_WEB_ROOT:-}" "docker://$(warden env ps -q php-fpm)/var/www/html"` at /opt/warden-m1/commands/sync.cmd:45 failed with exit code 1

I'm not sure how many people use this fork... if any? I haven't really announced this fork publicly so very little people know about it.

So... can one use this fork for their daily client work? If the version you need is listed on the README, yes! Most of the versions can be adjusted for another, but PHP cannot. So if you are okay with PHP 7.4 currently, perfect. For PHP 7.3 and 8.x, it will take time as I'm stuck on this Mutagen issue. You can absolutely use this fork on my M1 Pro/Max Mac with the mainstream service versions and have absolutely no issues. It's blazing fast. If you do encounter issues, please create an issue and I'll try to get it fixed ASAP.

Regards,
Adarsh.

[erikhansen]

@drpayyne Thanks so much for your detailed reply!

Some of our merchants are still using PHP 7.3 (but not for too much longer), so I'll probably keep my old MacBook Pro around for those clients and then use your fork for all PHP 7.4 projects.

I look forward to having a blazing fast machine!

[drpayyne]

Just an update, I do have 7.3 support now, but it uses Debian instead of CentOS like original Warden does.

[wintermute-84]

Hello @drpayyne
First of all thank you for your work.

After switching to docker, I've abandoned my MacBook for magneto development. Currently basic Thinkpad model running ubuntu is achieving load speeds with disabled FPC and block_cache of ~1s on all pages. Which is a bit faster then my previous vagrant setup with NFS on 2015 Intel MacBook Pro.

I'm considering an M1 Pro/Max purchase.

Can you please share your experience regarding load speeds of magento on your warden fork? I'm guessing it's still using mutagen for file sync?

Thank you.

[drpayyne]

Hi @wintermute-84, thank you for checking out this fork!

Regarding performance, it's very very good. It's extremely better than Intel Macs for sure. Yes, this still uses Mutagen. The only thing I've done in this fork, is switch to Debian and rebuild all Docker images for Apple Silicon.

This does have minor issues regarding syncing the SSH keys, etc. But I use this on a daily basis for my client projects.

[mattkrupnik]

Hi, any syncing the SSH keys update?

[erikhansen]

@mattkrupnik For what it's worth, I even had issues getting the SSH key to work in the main Warden build on my Intel Mac. I have a warden_add_ssh_key.txt file on my desktop whose contents I copy-and-paste into a warden shell session which adds my private key and authenticates it for the rest of that session. I've continued using this for warden-multi-arch. See attached file.
warden_add_ssh_key.template.txt