EE Trial License and bunfig scoped pkg's config not working on the second instance as desired
Is there a limit on my EE trial license: I see that the portal says 1 seat. So far, I have only had 1 docker-compose non-prod on my laptop, and one in Fly not marked non-prod, but it seems I can't pull private packages on the Fly instance even though I am running with the EE images and the license key is set. There were some difficulties in initial setup with migrations taking longer to get the lock, they eventually finished and I am not seeing any other difficulties other than not being able to pull the scoped npm packages listed in my bunfig in the instance settings. The same setup has worked well on my laptop with the docker-compose. So any help would be appreciated.
Bottom line is when its not working, it likes to resolve the scoped packages in the bunfig from npmjs.org and 404s obviously. Bunfig is actually pointing to GitHub. The documentation confuses me where it says to set up the npm private registry. Is it necessary to do that and set up bunfig - on my local instance, the problems finally went away when I just had the bunfig set.
However, the same working config is not working on the non-prod instance. Tried doing a
docker compose down to see if its a limit on the license seats causing the issue.
PM if you would like login to my instance. (Btw, this is Charandas - I use this moniker for my nonprofit work)2 Replies
It's not a limitation of the EE license
Not sure what the issue is if you can't reproduce locally
I know some people had issue with fly and private packages for some reasons
it stopped happening soon after, so i am not sure if the instance can get into a state, where some cache needs to be busted post installing the license.