Closed reavessm closed 5 years ago
No point in anonymising you PUID and PGID. It's also good for us to have fusing troubleshooting.
I have tried to access this via an existing reverse-proxy, as well as locally. Both have the same result.
I can get the container running, the issue, at least I think, is because the '/config/www' directory only has an empty 'plugins' directory and nothing else.
Assuming /mnt/VMStorage/Codiad
is a remote mount, Try putting it on your local file system.
@j0nnymoe That worked! I created a ~/Codiad
folder, mapped that to config, and it came up on the first try! But I have other containers running on that NFS share just fine? My ~/Codiad
directory actually has less permissions (755 vs 775 with the other).
Yea we get this alot. We don't recommend putting /config
mounts because stuff that uses sqlite etc don't like it.
@j0nnymoe is there a sub directory that I can mount on NFS shares to hold the source files? Can I map like /config/projects
on the share? I'm fine with user config stuff being wherever, but if I have a lot of projects, I don't want them cluttering things up
Actually, this might not have been fixed. It's been trying to create the initial project for about 10 minutes now, and it's still spinning. Also the /config/projects
directory is completely empty
Only thing I can suggest is try it and see what happens.
Add in -v /path/to/host:/config/projects
.
Just a heads-up @reavessm
We're in the process of deprecating this and releasing an alternative IDE as Codiad is no longer maintained upstream.
Command run:
When I log into 'https://localhost', I am greeted with the nginx '403 Forbidden' page. After digging through the code I found that /config/www/index.{html,php} does not exist. I then ran
echo "Hello" >> /local/path/ww/index.html
and revisited the site. Then I could see the 'Hello' message. This also seemed to happen when using HTTP as well as HTTPS.I was running this on Gentoo Linux, docker version was 18.09.5, image version was latest.