My old instance never worked. I'm setting a new one, this time on Docker. While adding details and an image I wanted to remove the text overlay in the instance's image (it's already its logo/name, it doesn't need it twice), that led me to CSS. I took the fastest tutorial on CSS and used the uBlock Origin picker tool as a makeshift CSS selector finder, worked every time. Unfortunately the > character kept being escaped when entered in the settings area.
I don't know if that's something in Funkwhale's code or NGINX, since I normally wouldn't go for NGINX because I don't understand it as much as I get httpd, I used the configuration offered in the guides. In a way, I guess that'd be Funkwhale's code too, then. ( 🤔… )
I digress. Again, I remember having seen the custom.css file, I just had to find it. When I did, I put my code there (which I got by sloppy-replicating the object on a web design app, applying styles, re-adapting), popped open the dev tools so Firefox would actually obey to ⇧⌘R and it worked! 🎉 On the first try, too. I didn't have to reference it as indicated (and I hadn't noticed it before in the dev tools either).
There was one issue though: the image was cut off (this is on /about, BTW). But, if I adjust it, then it wouldn't fit on /about/pod because it's the same image, but armed with my new rudimentary CSS tricks skill I got to work on new code to center it and contain it within the its parent element, that led me to like the fourth, fifth? IDK the next issue: its location.
The source goes:
<section class="ui head with-background vertical center aligned stripe segment" style="background-image: url("…/media/dynamic_preferences/instance__banner/someimage.png");"><h1><i class="music icon"></i> sometitle </h1></section>
I would add:
.segment.stripe.aligned.center.vertical.with-background.head.ui {
background-image: center / contain no-repeat;
}
Hoping the attributes would merge or overwrite, maybe experiment with !important IDK, but first I refocused on what I read in the source; the path.
— "key=media. Hmm…", I thought.
I searched for "media" in the docker-compose .env file which confirmed what I was fearing, it's the same directory for media files, whereas (AFAIK) images like these are normally classified as "assets", aren't they??
That's wrong in soo many levels, especially since it's described as such:
— "Albums covers or audio tracks"
However, if you go a few lines further, there's a much more suitable directory (I think):
So, I'd like to learn how to reference that from the web, or any other place outside of /media/. Could you tell me which directories are available on the frontend (and their path)?
The alternative would be separating my music and making it fully managed by Funkwhale, but it's much faster moving a few kilobytes of data than multiple gigabytes in small files and in thousands of tiny slow-moving supporting metadata files. :/
Thanks!
