ACF Pro as a Composer dependency (without committing your license key unencrypted)

trellis
51

Huh! Good catch. I’ll see if I can make a pull request for @philippbaschke today or tomorrow.

4 Likes
52

In the meantime this drop-in replacement could be used:

4 Likes
53

Hi!

Just chiming in here. I got tired of custom solutions for all different premium plugins i needed when developing WordPress with Bedrock. After some research i found Release Belt, nice way to setup an own private Composer repo. I wrote up a tutorial about it in a blog post if anyone is interested, a way to not only handle ACF, but all premium plugins.

Best regards
Samuel Horn

54

This means having a zip file for each version yeah? To me that doesn’t seem to alleviate the pain point of logging in to each premium plugin’s “my account” page and downloading the latest version. SatisPress works much better imo. I wrote about it.

55

I am a bit confused as I assumed that adding env variables in #trellis to /group_vars/all/vault.yml such as

vault_wordpress_sites:
  example.com:
    env:
      ACF_PRO_KEY: A-UNIQUE-KEY-AJHDIUHDW/Z/(ADIHDSAJK

would add the key to the .env at provision as it does for the environment specific vault.yml.
Just tried it for a couple of times but the variables from /group_vars/all/vault.yml are not added to .env. Don’t you agree that this would be very useful, as you do not have to set the same variable three times for development, staging and production. Or do I someting wrong?

Cheers and best regards

56

You can use vault_wordpress_env_defaults (introduced by @TangRufus in https://github.com/roots/trellis/pull/1048)

2 Likes
57

Very useful hint! :slight_smile: Thanks!

58

I followed the guide > ACF Pro as a Composer dependency (without committing your license key unencrypted) - trellis - Roots Discourse on my staging environment ACF Pro is installed without problems when I deploy, but on my development environment I receive this error when I run composer update

[FFraenz\PrivateComposerInstaller\Exception\MissingEnvException]
  Can't resolve placeholder {%ACF_PRO_KEY}. Environment variable 'ACF_PRO_KEY' is not set.

I added the acf_pro_key: “xxxx” in the trellis/group_vars/development/vault.yml (as i did for the staging vault file) but on development environment it doesn’t work.

I suppose that the problem is this one:

how can i re-create my .env file in the development environment?

thanks

59

Run vagrant up --provision or just add it manually

60

thanks @Twansparant, it is ok now, I run vagrant reload --provision
I noted for the next time, thanks again :wink:

1 Like
61

Hello all,

I am excited to start working with Bedrock and came across this article. Very helpful but it assumes you are using Trellis. Is there an alternative approach for being able to use ACF Pro without Trellis? Thank you

62

It should be pretty much the same except you’ll just put the ACF key in your .env file manually rather than having Trellis create the .env on deployment. Does that make sense?

1 Like
63

Ah… great. Thank you!

64

Is it possible to update the documentation to reflect the update of private-composer-installer? The version currently included is conflicting with phpdotenv but the author recently published a new version (4.0) that fixes the bug.

1 Like
65

I use Bedrock/Trellis but only to deploy to kinsta. That means no local Vagrant deploy. I attempted the method to load ACF Pro with the license key in vault.yml.

When I run composer update on my local repo, it can’t resolve the ACF_PRO_KEY environment variable. This makes sense because there actually isn’t a local .env, it is on kinsta.

Running ansible deploy to kinsta does populate the .env file with the ACF key, However, the plugin doesn’t install because composer update failed and didn’t update composer.lock before deployment.

Seems a catch 22 here. There is no local deploy or local .env, but the remote deploy to kinsta needs there to be one.

Any thoughts for Kinsta/Trellis folks trying to use ACF Pro?

66

For local development, the key should be in the local .env file.
But for remote, the vault file and Trellis deploy should be already sufficient.
Be sure that the same variable name as in the composer.json is used among the local dev .env and Trellis vault files.

67

I don’t care much for how this tutorial requires the consumer to bump the plugin version manually anytime there’s a release.

Created this as a general-purpose alternative.

3 Likes
68

This is wonderful! Thank you for this contribution!

69

Update the link looks like this now: https://connect.advancedcustomfields.com/v2/plugins/download?p=pro&k={%ACF_PRO_KEY}&t={%version}

3 Likes
70

ACF have created their own way to do this now.

The news article:

The ACF guide:
https://www.advancedcustomfields.com/resources/installing-acf-pro-with-composer/

How we can use it:
https://roots.io/trellis/docs/composer-http-basic-authentication/

5 Likes