tko

joined 1 year ago
[–] tko@tkohhh.social 3 points 2 months ago

I run a Nextcloud instance on my Unraid server.

[–] tko@tkohhh.social 5 points 2 months ago (1 children)

I hear you... it's definitely not about one tasting better than others, but maybe more about the eating experience. I do think there's a legitimate argument about how different pasta shapes encourage different pasta to sauce ratios, but at the end of the day it's just the two elements coming together and the taste is what it is. We should all enjoy it the way we want to! I just wanted to explain why some people talk about certain sauces and certain pasta shapes "belonging" together.

[–] tko@tkohhh.social 6 points 2 months ago (9 children)

It has everything to do with the consistency of the sauce and how well it sticks to the pasta. For example, spaghetti with a meat sauce isn't a great choice because the meat won't actually stick to the pasta and you'll have to scoop up that meat "manually." Better is pappardelle, which has a huge surface area that causes the meat to stick to the pasta.

[–] tko@tkohhh.social 1 points 3 months ago

Eh, what's gonna happen is gonna happen regardless if I pay attention to it or not... I guess I just prefer not to worry about it!

[–] tko@tkohhh.social 2 points 4 months ago

Indeed. A wise wizard once said: "It is a curious thing, Harry, but perhaps those who are best suited to power are those who have never sought it."

[–] tko@tkohhh.social 2 points 4 months ago

It was not a prediction of victory... it was a 71% chance of winning the electoral college. Said another way, they gave her a 29% chance of losing.

https://projects.fivethirtyeight.com/2016-election-forecast/

[–] tko@tkohhh.social 2 points 4 months ago

ahhhh yes, that makes perfect sense... thank you for pointing that out! Especially since I'm not good enough with vi to know how to bulk delete the first character in specific lines, I had to manually arrow and delete.

[–] tko@tkohhh.social 2 points 4 months ago* (last edited 4 months ago) (2 children)

I successfully migrated postgres 15 to 16. I followed the general idea of the guide you posted, but I found it a little easier to do a slightly different process. Here's what I did:

  1. docker-compose down for the lemmy instance

~~2. edit the docker-compose.yml file and comment out all of the services except postgres. In addition, add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles~~

  1. edit the docker-compose.yml file and add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles
  2. docker-compose up -d postgres (this starts just the postgres service from the docker compose file)
  3. docker exec -it [container name] pg_dumpall -U [username] -f /miscfiles/pgdumpall20240628 (I think this will work, but it's not exactly what I did... rather, I ran docker exec -it [container name] bash, and then ran pgdumpall -U [username] -f /miscfiles/pgdumpall20240628. The end result is a dumpall file saved in the ./volumes/miscfiles directory on the host machine)
  4. docker-compose down
  5. mv ./volumes/postgres ./volumes/postgresBAK20240628 (move your existing postgres data to a new directory for backup purposes)
  6. mkdir ./volumes/postgres (re-create an empty postgres data folder. make sure the owner and permissions match the postgresBAK20240628 directory)
  7. edit the docker-compose.yml and update the postgres image tag to the new version
  8. docker-compose up -d postgres (you'll now have a brand new postgres container running with the new version)
  9. docker-exec -it [container name] psql -U [username] -f /miscfiles/pgdumpall20240628 (again, I think this will work, but I bashed in and ran the command from within the container. This also allows you to watch the file execute all of the commands... I don't know if it will do that if you run it from the host.)
  10. docker-compose down

~~12. edit the docker-compose.yml and un-comment all of the other services that you commented out in step 2~~

  1. docker-compose up -d

Hopefully that helps anyone that might need it!

edited to reflect the comment below

[–] tko@tkohhh.social 6 points 4 months ago

I agree... I was simply clarifying that Nate Silver did NOT predict that Hillary would win (nor is he predicting that Trump will win this election), which is a common misunderstanding about probability. For these types of models to be meaningful to the public, there needs to be literacy on what is meant by the percentages given. Really, I'm just reinforcing rodneylives' point from another angle!

[–] tko@tkohhh.social 11 points 4 months ago (3 children)

I don't remember him predicting that she would win. His model (https://projects.fivethirtyeight.com/2016-election-forecast/) gave her a 71% chance of winning. 71% is a long way from 100%, and the result of that election definitely fit within the model.

That said, you are absolutely correct... we need to keep shining a light on the realities of each of these candidates, because in the light of day Biden is a much better choice than Trump.

[–] tko@tkohhh.social 1 points 4 months ago

Thank you, that's super helpful!

[–] tko@tkohhh.social 3 points 5 months ago

Stop j'terrorizing me!

 

I'm a little confused as to how the "report" function works. I'm an instance admin, but if I report a post on another instance, that report shows up in MY report queue. If I mark that report as "resolved" to get rid of the notification count, does it resolve it on the home instance?

 

I'm curious what everyone thinks about the posts that have shown up here that are simply a link to purchase an item on Amazon?

These posts are coming from users that don't have any other engagement other than these posts. This does not seem like a good-faith effort to engage with the community, but rather a cheap attempt to generate clicks and sales.

I would like to see these posts banned, but I'm curious how the rest of the community feels.

 

49ers that made the list:

  • #79 - Dre Greenlaw
  • #78 - Talanoa Hufanga
  • #61 - Deebo Samuel
  • #35 - Christian McCaffrey
  • #19 - George Kittle
  • #15 - Fred Warner
  • #14 - Trent Williams
  • #4 - Nick Bosa
2
submitted 1 year ago* (last edited 1 year ago) by tko@tkohhh.social to c/lemmy_admin@lemmy.ml
 

Unfortunately, the official documentation on theming lemmy is severely lacking. I made some progress on getting it figured out today, so I wanted to share that with you all.

This is by no means meant to be an exhaustive guide, but my hope is that it will at least get you going. I'm sure that I will say things that are incorrect, so please correct me if you know better!

Background

Lemmy uses Bootstrap-compatible theming. As far as I can tell, this means that it uses a pre-defined set of CSS classes. This is important because if you provide a CSS file that doesn't have all of the correct classes defined, it will break the layout of your lemmy.

Your custom CSS needs to be saved in the bind mount for your lemmy-ui container. If you followed the install instructions on join-lemmy.org, the location will be /lemmy/volumes/lemmy-ui/extra_themes/.

Prerequisites

In order to generate the correct CSS, you need a couple of things:

  • your customized Bootstrap variables, saved in an scss file
  • the Bootstrap scss files
  • the SASS compiler

Let's go through each of these (last to first):

The SASS compiler

The SASS compiler needs to be installed on the machine you will use to generate your CSS files (it doesn't NEED to be the computer that lemmy is installed on, but it can be). Follow the install instructions relevant to you. I used the "Install Anywhere (Standalone)" instructions and installed SASS on the Ubuntu machine that is running my lemmy instance.

The Bootstrap scss files

These files need to be saved on the same machine as the SASS compiler. The Bootstrap download page has a button to download the source files ("Download source"). This will give you a zip folder, so unzip it. Within the unzipped files, the only directory you need to keep is /bootstrap-5.3.0/scss. Save that folder in a place that makes sense for you. I put it in my home directory, so the path looks like ~/bootstrap-5.3.0/scss. You'll need to reference this directory when you're creating your custom scss file.

Your customized Bootstrap variables, saved in an scss file

This is the fun part... you define your Bootstrap variables. I'm still a little unclear on which version of Bootstrap lemmy is using (and therefore which variables are valid), so I chose to start with one of lemmy's default themes as a starting point. I grabbed _variables.litely.scss and litely.scss from the lemmy-ui github repo as a starting point.

You'll notice that litely.scss is just importing variables.litely as well as the Bootstrap scss files. You'll need to change the path of the Bootstrap scss files to the path where you saved your copy of the files. However, leave bootstrap at the end of the file path, as this is actually referring to the bootstrap.scss file within the Bootstrap scss directory.

It wasn't obvious to me initially, but you can also add your own CSS styles at the bottom of your scss file. These will be merged with the styles defined in the Bootstrap files. For instance, I wanted my navbar to have a different font from the body, so I added this:

#navbar {
  font-family: sans-serif;
}

Generating the CSS file

Once you have all of the prerequisites satisfied, you can generate your CSS files using the SASS compiler. Go to the directory where your customized scss file(s) are saved, and run this command (you added the SASS install directory to your PATH, right??):

sass [inputfile.scss] [outputfile.css]

This will generate a CSS file. However, pay attention, as there might be errors. If so, fix the errors until you can run SASS without any errors.

Finally, drop the generated CSS file into your "extra_themes" directory. You'll now see your theme show up in the list of themes on your profile (it'll be the filename of your CSS file).


And that's it! I hope somebody finds this helpful. Please let me know if there's anything I can clarify!

view more: ‹ prev next ›