Runcloud itself installed ngnix, apache, php, mysql, etc so the only thing I had to do was updating nginx to the newest version. And I did it.
But the issue now is Ghost-cli tool doesn’t see my ngnix folder, because Runcloud named it nginx-rc during its own configuration process, so I have etc/nginx-rc folder. But one more issue might be with sites-available folder…I simply don’t have it inside etc/nginx-rc/
By the way, I want to keep the ghost install on the same droplet which is running Runcloud with its WordPress websites.
There’s an undocumented feature that allows you to use an environment variable to override the config path for nginx. Details in this PR:
Providing it still runs as nginx, you should only need to set NGINX_CONFIG_PATH. You can use this when running commands, but if you set it globally on the machine you won’t have to think about it again
Thank you, @Hannah!
I’ve deleted my follow-up comments because they were unnecessary. You provided a clear answer.
(for new readers):
I marked Hannah’s respond as a SOLUTION because running the following command: export NGINX_CONFIG_PATH=/etc/nginx-rc
before dealing with ghost cli helped me to install Ghost CMS with SSL on a Runcloud-managed VPS.
In 2025 it’s already possible to install Ghost CMS from the Runcloud Dashboard (UI), no need to open the terminal.
