A) I'm not American
And
B) America can go fuck itself until it sorts out it's Nazi problem. I still think Canada should enact a full trade embargo and take our business elsewhere.
Darkassassin07
joined 2 years ago
It appears white/gold to me on it's own, I've never been able to see anything different.
Grabbing this specific image and sampling the colours though; they appear more of a grey/brown colour. I can sorta maybe understand blue, but definitely not black.
This is just using Polish photo editor on android:
Here's the one Colin Furze built a couple years ago in his workshop. He only took it down a few weeks ago to reclaim the space.
There's also an older one on his channel that he built over 17 years ago, out of pallets in a field.
If you've ever worked customer service, you know that automatically providing instructions is warranted; half the people you run into in public would struggle to operate a spoon without guidance.
I'm not sure whether this is specific to this project, docker, or YAML in general.
Looking through my other 20 or so compose files, I use the array notation for most of my environment variables, but I don't have any double quotation marks elsewhere. Maybe they're not supposed to work in this format, idk.
Good to keep in mind I guess.
What part of this is satire?
Pop-up headlights disappeared because they were a PITA to maintain in working order.
Sooo many 'winking' cars because half the popups don't work, which is a massive saftey issue.
Dev replied to my github discussion.
Apparently it's an issue with array style env variable layout.
environment:
key:"value"
Instead of
environment:
- key=valueTrying to set that up to try out, but I can't get it to see/use my config.yaml.
/srv/filebrowser-new/data/config.yaml
volumes:
- /srv/filebrowser-new/data:/config environment:
- FILEBROWSER_CONFIG="/config/config.yaml"
Says '/config/config.yaml' doesn't exist and will not start. Same thing if I mount the config file directly, instead of just its folder.
If I remove the env var, it changes to "could not open config file 'config.yaml', using default settings" and starts at least. From there I can 'ls -l' through docker exec and see that my config is mounted exactly where it's supposed to be '/config/config.yaml' and has 777 perms, but filebrowser insists it doesn't exist...
My config is just the example for now.
I don't understand what I could possibly be doing wrong.
/edit: three hours of messing around and I figured it out:
- FILEBROWSER_CONFIG="/config/config.yaml"
Must not have quotation marks. Removed them and now it's working.
Live sports is one of the only things that still makes sence to have live tv for. Pirate sources for live games is difficult; but I'm not much of a sports fan anyway, so that's never really enticed me.
Woops
I missed that; bit of a sensitive topic atm...