Page 1 of 1
sed -e no such file or directory
Posted: Sun May 26, 2024 2:14 am
by mothravsmechabilbo
I'm getting this error every time I get to a certain part of the install process, and I can't tell what file or directory it is referring to. I have no issues until this point, i.e. selecting the media directory is fine. Can anyone tell me where to dig?
What's your VPN password? (if you are using mullvad, just enter your username again): *
Configuring the docker-compose file for the user "administrator" on "/opt/yams"...
Copying docker-compose.example.yaml to /opt/yams/docker-compose.yaml...
docker-compose.example.yaml was copied successfuly!
Copying .env.example to /opt/yams/.env...
.env.example was copied successfuly!
Copying docker-compose.custom.yaml to /opt/yams/docker-compose.custom.yaml...
docker-compose.custom.yaml was copied successfuly!
sed: -e: No such file or directory
Re: sed -e no such file or directory
Posted: Sun May 26, 2024 2:15 am
by mothravsmechabilbo
I'm on macOS 14.5 by the way.
Re: sed -e no such file or directory
Posted: Sun May 26, 2024 11:55 am
by rogs
Hey @mothravsmechabilbo!
MacOS is not supported by YAMS. https://yams.media/install/steps/#dependencies
The YAMS installer depends on GNU sed
which is not the same one that comes with MacOS. You might be able to install YAMS manually by following the docker-compose documentation and making changes manually.
Cheers!
Roger.
Re: sed -e no such file or directory
Posted: Sun May 26, 2024 4:30 pm
by mothravsmechabilbo
Thanks @rogs, that's what I'm planning to do now. When you say make changes manually, do you mean filling in the vars in the docker-compose which I would have populated via the install.sh instead? I plan to have a .env file for the guid and media location and such (basically copying the env file that was already in the YAMS repo. Beyond editing the compose file, however, is there anything else I should be aware of?
Re: sed -e no such file or directory
Posted: Sun May 26, 2024 4:52 pm
by rogs
Nothing more! Only replace the variables from the .env on the docker-compose or use your own .env file. Either should work