using a mediasoup media node
we have just deployed a new openvidu environment in aws using the cloudformation template latest.

the version reported is 2.19.0. the system is licensed with a pro license.

we have changed the .env variable openvidu\_edition to enterprise and ran the restart command.

when we add a new node it stil…
don’t worry, possibly you’re using mediasoup, just the name of the media nodes still being named as kurento media server.

to check if mediasoup is running, just ssh into one of the media nodes machine and execute this:

sudo su

docker ps | grep mediasoup

you should see a container using this image…
Did you had ACS common installed in your AEM.

<https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html>




[View solution in original post](/t5/adobe-experience-manager/aem-implementation-of-versioning-for-clientlibs-and-css/m-p/399346#M7116) Apparently you have a version of NodeJS that does not understand the new features of ES6+, update.  

Way to put on the server, NodeJS and VueCLI at least strange. You were unfortunately fooled by the marketing. The actual updated Lightroom is called Lightroom Classic. It is exactly like you remember with a develop panel, ability to print, etc and will behave and work like the Lightroom you are used to. What you likely installed is a port of the mobile operating system version of Lightroom to desktop operating systems. Adobe calls this Lightroom Desktop which is extremely confusing. What you want to do is to call adobe and transfer your subscription to Lig... the filename should be .env not environment.env. [image] slo-motion:

for yabridge, wine4.0.3 is too low

hit me upside the head…

this must be how you ended up with the ubuntu groovy repo. ok… we need to…

remove wine…

again…

and try to install the later version as if this was ubuntu 18.04.

let’s get to work. in terminal

sudo apt remove… The download is an updated version. hi erin

a website restart is required to pickup some changes to settingitems in the portal, id recommend giving it a restart and it should show.

regards
joe hi kenhaught, thanks for your replies. i finally fixed the problem. i had built the vms on a previous version of esxi, version 5.5, so they had an earlier vm version of the hardware. once i updated the hardware version, of the guest, to "esxi 6.5 and later (vm version 13)" the windows server 2016 option appeared. it is pre-installed as part of the newer upgrades hi and welcome!

it’s not an open ondemand thing. you need to setup sshd to allow for hostbasedauthentication and generate some key pairs. this setups some sort of trust between 2 or more servers saying “if you’ve logged into one of them, you can login to the other directly”.

of course we use lots…