Dandroid

joined 1 year ago
[–] [email protected] 1 points 1 year ago

Leeloo Dallas Multiclass

[–] [email protected] 7 points 1 year ago (2 children)

Only bad teachers have ever said that. But I doubt they do now that everyone has a calculator on their phone.

[–] [email protected] 0 points 1 year ago (1 children)

When does this come out for the general public?

[–] [email protected] 3 points 1 year ago

Literally this morning I started getting boot errors. It is telling me WBM can't find the boot file. But I should be booting into grub, so idk what to do. My boot order is Ubuntu, then USB. And that's it. And now I'm out of the house all day and can't do anything but sweat about it.

[–] [email protected] 3 points 1 year ago (1 children)

Last Christmas. It's the Christmas one night stand song. And it just repeats the same thing a thousand times. Turn that shit off.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

If you post the link in the format [email protected], you can open it from any instance and stay on that instance.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Your cat is so lucky to have such an amazing human to go above and beyond to make sure he has something that's safe for him to eat. Keep being awesome. And thanks for sharing this info!

[–] [email protected] 1 points 1 year ago

Not having to do a database rollback is a really, really hard problem to solve, and it would almost certainly need to be on the Lemmy developers side, not the server owner's side. And if I'm them, that's a low priority issue, and probably not something I even think about until 1.0.

Basically, they write code that says what to do in the event of a database version change. Usually this only handles upgrade cases, because that's what happening most of the time. One example of something you might do in a db upgrade is let's say you had a column where the data type was only numbers, but now you want to allow any alphanumeric character for some reason. You could have a line of code that converts the number to a string.

Okay, but now you need to go back to the previous version. Okay, your db change code runs, but it's the old version of the db change code, not some new version that you wrote. You unfortunately didn't have a crystal ball when you wrote this code and couldn't predict that you were going to change the data to strings, so you didnt write code to change it from a string to a number.

This is why most software doesn't support downgrades unless you wipe first. For example, if you updated your aging MacBook to the latest Mac OS version, then realized it slows down your laptop too much, you can only go back if you first wipe your laptop in the process. So it's just easier to just take a snapshot before an upgrade and revert to the snapshot if it fails. Some folks will even do "scheduled maintenance" time during the upgrade in which the whole system goes down for a short time so they don't have to risk losing data that happened after the snapshot.

[–] [email protected] 2 points 1 year ago

If they know you are free. 😉

[–] [email protected] 5 points 1 year ago (1 children)

I learned about this http response code too late. About 4 years ago I was working at a startup and I was the "lead engineer" (aka only engineer) on a project where I had to design and implement an entire REST API. I really wish I would have put this in somewhere, since we weren't doing code review (because it was literally only me).

[–] [email protected] 2 points 1 year ago

I just throw bacon on the barbecue at the same time as my burgers. It takes almost the same amount of time to cook, and it's super crispy - just how I like it.

[–] [email protected] 1 points 1 year ago

All the bot accounts come from this instance.

 

I just tried fetching the community [email protected]. Other instances seem to be able to make this request and get the results, but for some reason, it is coming up empty for me.

 

I tried for several days to host lemmy 0.17.4 using the docker install instructions, but I was less than successful. The instructions seemed to be riddled with mistakes and and the docker-compose.yml file had some errors. I eventually mostly got it up and running, but I could never access the site through the nginx container. I had to add the lemmy-ui to the external network and expose 80 and 443, and then I could access the UI. But it seemed that the UI was unable to communicate with the DB. And I had to comment out all of the loggers in docker-compose.yml, because I they were giving me errors.

Anyway, I thought I would give it another shot now that 0.18 has been released and the instructions have been updated. It seems to be much better! I was able to almost get it up and running on my first try. However, there is one error. The nginx container failed to start. There is a file it is trying to mount, but the file doesn't exist. And the instructions don't seem to say anything about creating that file or where to download it.

Any help would be much appreciated!

The instructions I am following: https://join-lemmy.org/docs/administration/install_docker.html

The error:

Creating lemmy_proxy_1    ... error

ERROR: for lemmy_proxy_1  Cannot start service proxy: crun: mount `<path>/lemmy/nginx_internal.conf` to `etc/nginx/nginx.conf`: Not a directory: OCI runtime error

ERROR: for proxy  Cannot start service proxy: crun: mount `<path>/lemmy/nginx_internal.conf` to `etc/nginx/nginx.conf`: Not a directory: OCI runtime error
ERROR: Encountered errors while bringing up the project.

Edit

I ended up finding the file in the lemmy-ansible github project here: https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx_internal.conf

It all comes up now, and I can access it from outside the server. Though, it is http only, even though I have https set to true in docker-compose.yml. And when I try to do the admin sign up, I get the error: SyntaxError: Unexpected token 'O', "Origin is "... is not valid JSON

Edit 2

It's all working now. I'm not sure exactly what I did. I set up my https cert by modifying the nginx_internal.conf and adding ssl details, and now it all works. 🤷

Thanks for the replies!

 

The was back in the winter when it was cold. She first went under the blanket completely, but after a few minutes, she poked her nose out like this.

 
 
 
 
 
 

Mikei couldn't fathom that I was taking a picture of something other than her, so she had to jump in.

 
 
 
view more: next ›