morethanevil

joined 1 year ago

Then you need an import function too 😁

But I like the idea of backup and restore functions, so I agree

Last update 2022, same with podgrab. I hope the dev is okay 🫀

[–] morethanevil@lmy.mymte.de 1 points 1 year ago (1 children)

Alexandrite selfhosted eith my instance. Looks far better than Lemmy UI

[–] morethanevil@lmy.mymte.de 5 points 1 year ago* (last edited 1 year ago)

You can filter a search for Videos <-4 minutes

At the moment there is no real "shorts"

[–] morethanevil@lmy.mymte.de 9 points 1 year ago (4 children)

Maybe Peertube will match your needs ☺️

It is part of the Fediverse too.

Yes I prefer anisearch because the main site is german 😁

But everybody can always copy the title, it should be the same on MAL

And yes, it is a great Anime, I enoyed both seasons 🌞

A new Subdomain is like a whole new instance. I would not move over old posts or something else.

Start completly fresh and have fun instead of headaches because of broken Posts 🌞

You can try your setup with another subdomain. This way you will see If there are any problems

And never lose your database. It is the heart of your instance, so do proper backups ☝🏻

Yes the dev made huge progress the last few weeks I wish you good luck with your instance. I subscripted to pixelart already 🌞

You can change the folder structure but I don't think that matters. Rclone your libary folder and that's it. If you want to save some space, exclude thumbs and encoded videos folder. You can take out videos and images if you ever need your backup.

Never had any problems 🌞

[–] morethanevil@lmy.mymte.de 10 points 1 year ago (2 children)

Never had any breaks with immich. Immich libary is backuped daily to external provider. Data Retention is managed by them, so I only need to run my scripts.

The libary (upload folder) is the only thing you need to backup. I don't think it is more complicated than any other folder with subfolders. You can always start from zero

I use rclone for automatic backups from my server, Immich included 🐱

[–] morethanevil@lmy.mymte.de 21 points 1 year ago (1 children)

An option to set a cache limit would be nice. Caching is okay, as long as you can clear the cache. Something like Mastodon caching. You can prune all remote media via tootctl

Turning completly off will increase the traffic of all other instances -> longer loading times πŸ€”

 

From the series Akame ga Kill

Source

 

From the School live series

Source

36
submitted 1 year ago* (last edited 1 year ago) by morethanevil@lmy.mymte.de to c/selfhosted@lemmy.world
 

I would like to introduce a reverse proxy which I really like to use and maybe you will like it too 😊

I tried a few reverse proxies, but in the end nothing met my needs. A simple reverse proxy with webinterface, easy to setup, but powerful...

I was impressed from the start with Zoraxy. A good alternative to Nginx Proxy Manager and Cosmos. Zoraxy can be run in docker, but it is possible to install it directly on the host. This is the first reverse proxy I saw, where docker is not an obligation (except apache and nginx itself :) )

Zoraxy makes it easy to setup subdomain proxies oder virtual directory records. An uptime Monitor is included too and a few network tools like ping, whois, mDNS scanner, IP-scanner or a ssh client.

LetΒ΄s Encrypt is supported and custom certificates. Blacklist / Whitelist access control and a lot of stats (like goaccess but with better diagrams)

You can import and export all settings to zip file including all subdomain proxies etc...

Read more and try out on GitHub

I am not the developer but I really like this project!

 

I was looking a long time for a policy which binds a user to a bucket. The docs are not very helpful for beginners, but I talked with an advanced user and he said it is okay to share his solution, since he is not on Lemmy

Create a new policy and fill this in:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": [
                "arn:aws:s3:::${aws:username}"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": [
                "arn:aws:s3:::${aws:username}/*"
            ]
        }
    ]
}

If you now create a user, just assign the user to only this policy, nothing more. The user is now allowed to create a bucket with the same name as the users. So a user Alex can only create the bucket alex and has complete access to it. The user won't see other users buckets.

All credits belongs to the very helpful person, not me ☝🏻☺️

 
 

Source :)

 

From the great movie Suzume

I really enjoyed this movie in the cinema 🐱

 

From the same named series and the game

 

A random but beautiful picture found on the net a long time ago

 

From Anohana :)

 

Raphtalia & Naofumi from "The rising of shield hero"

view more: next β€Ί