I have the folder. I chown and chmod it as it should be. Looks like it reverts back to the wrong permissions though. Don't know why.
I manually set it to 777 several times for testing purposes, but apparently, it switches back to 700
Thanks for trying. The issue you mentioned helped me before to have it spinning. I feel like I've tried everything mentioned in the docs as well as what I am aware of and capable of 😅
Thanks for your answer. I'm not sure what to look for in the browser's logs but here it is.
I have logs for all containers here:
db. A lot of errors here, but I think I recall reading somewhere in the issues that it doesn't matter. I'd have to double check that.
I have one container exited, mediacms_migrations
, but I noticed it stopped right after the stack's setup and thought it would be used only for startup.
Here are the logs for it
db. A lot of errors here, but I think I recall reading somewhere in the issues that it doesn't matter. I'd have to double check that.
I can only answer for myself, but I use it to resume large downloads that failed and organize them.
While I run a couple headless debian at home, it's just for using docker and I only know the very basics.
It sounds like a badass solution, but it's over the top for me ^^
@Tiritibambix
@lemmy.ml