morethanevil

joined 1 year ago

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

[–] morethanevil@lmy.mymte.de 4 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.

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 🌞

[–] morethanevil@lmy.mymte.de 17 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 πŸ€”

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

Today there was a post about an art instance for Lemmy 😊

Maybe someone will create one on Pixelfed too

Nice, will share 😊

The only thing I am missing right now, is the ability to increase the icon size and community name under the post title πŸ€”

Do I overlook something?

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

I tried Arctius, it looks good but misses a few features. Maybe I give it another try in the future.

I use Liftoff, it is good but the design is a little bit boring, but Liftoff is very useable as a daily driver and works fine.

I discovered Connect yesterday, it is a good match if you want a good design and features. It has a new post button like Liftoff. I like this. Connect seems to be a good match for me.

Voyager was not my case, did not like it. Tastes are different. Same for Sync

For Mastodon, I use Moshidon. I like it very much

+1 for Quillpad 🌞

[–] morethanevil@lmy.mymte.de 18 points 1 year ago

One big DB will be a single point of failure. You will not benefit from much more speed, the only thing which is "easier" is backup.

I use different DBs for different stacks. If one hangs up or messed up completly, it won't affect others

34
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 ☝🏻☺️

view more: next β€Ί