[-] SinTan1729@programming.dev 14 points 1 day ago

Also, I hate the name of the column. The frequent mention of the name "Who, Me?" just takes me out.

[-] SinTan1729@programming.dev 1 points 2 days ago

It was just a matter of setting the correct user. In most cases, user: 1000:1000 should fix it.

5
submitted 1 week ago* (last edited 1 week ago) by SinTan1729@programming.dev to c/neovim@programming.dev

I simply want to emulate the effect of -p by default i.e. open all files in tabs when multiple files are supplied. I wrote the following autocommand to make it work.

-- Open files in tabs by default
vim.api.nvim_create_autocmd("VimEnter", {
    callback = function()
        if not vim.opt.diff:get() and #vim.fn.argv() > 1 then
            vim.cmd("tab sball")
            vim.cmd("tabfirst")
        end
    end,
})

But it seems to bork the colorscheme for all but the first tab. It's weird since Running the same commands manually after neovim is loaded works perfectly. I may have something to do with the order in which things are run. Is it possible to run this command as late as possible?

I'm open to alternative approaches that gets the job done.

[-] SinTan1729@programming.dev 3 points 2 months ago

That's a pretty good idea, actually. I'll try that out. Thanks.

[-] SinTan1729@programming.dev 2 points 2 months ago* (last edited 2 months ago)

Thanks, I took a look. It's very close to what I want, but it still doesn't support uploads in shared directories. It seems to be a pretty highly requested feature though. So maybe it'll happen at some point.

[-] SinTan1729@programming.dev 18 points 2 months ago* (last edited 2 months ago)

Storage, RAM, CPU usage. I prefer not to have such a large piece of software running for no reason. It might seem silly, but I hate using resources for no reason. I'll rather have 5 lightweight apps running instead of a huge one, of which I'll only use a few parts.

[-] SinTan1729@programming.dev 3 points 2 months ago

I'm strictly against Nextcloud or something similar. I prefer to run a bunch of lightweight apps, rather than one big one.

[-] SinTan1729@programming.dev 2 points 2 months ago* (last edited 2 months ago)

Yeah, but that's already possible with my current setup using FileShelter. I'd like them to be able to upload as well.

[-] SinTan1729@programming.dev 2 points 2 months ago* (last edited 2 months ago)

This looks pretty promising. Do you know if it's possible to add per-share passwords, so that I don't need everyone to open an account?

Edit: It's not.

[-] SinTan1729@programming.dev 7 points 2 months ago

Yeah, it's a bit too much I think.

69
submitted 2 months ago* (last edited 2 months ago) by SinTan1729@programming.dev to c/selfhosted@lemmy.world

I thought of this after a recent trip with some friends. We shared the photos when we were still in person. But sometimes we need to share a lot of photos over the internet. In the past, we have used a shared google drive directory for this. But I'd prefer a self-hosted option. There should be some sort of password protection as well (ideally per share, and no need for accounts). One should be able to both access the current files and upload new ones, just like google drive or dropbox.

I currently have FileShelter, which works for 1-to-1 sharing but not for groups. I guess something like ProjectSend would work, but it's too complex for my usecase. I'd prefer something more lightweight since I'll maybe use it once every few months. Also, it should be noob-friendly, and accessible using a browser.

Update: I'm very happy with copyparty. It does what I want, and much much more. I even replaced my older webdav server with it since it provides more granular control over share locations and permissions. Kudos to the developer @tripflag@lemmy.world!

3
submitted 3 months ago* (last edited 3 months ago) by SinTan1729@programming.dev to c/kubernetes@programming.dev

Someone added a PR to an app of mine adding instructions for k8s setup. I do like the idea of providing these instructions, but I don't have any experience with k8s whatsoever. The commits look fine to me, but in case anyone is experienced, I'd appreciate if you can take a look. I don't want to inadvertently add something malicious. Here's a link to the PR: https://github.com/SinTan1729/chhoto-url/pull/48, thanks.

[-] SinTan1729@programming.dev 2 points 3 months ago* (last edited 3 months ago)

Upon further testing, this does actually work. You may set both read_only: true, and cap_drop: all and it will work as long as you have a named volume. I had it mount a database file from the host system for my test config, which is why I was getting the errors. I don't know how to make that work though i.e. when the db is bind mounted from the host system. Setting the mount :rw doesn't seem to fix it.

[-] SinTan1729@programming.dev 3 points 3 months ago* (last edited 3 months ago)

Thanks. I had never tested this before. Seems like it throws errors. Of course, adding and deleting links don't work. But that's to be expected. But also link resolution fails since it cannot update the hit count properly. If this is a legitimate use case for you, I might work on making it work.

[-] SinTan1729@programming.dev 9 points 3 months ago* (last edited 3 months ago)

Like the other guy said, it's not necessary. But docker makes it much easier to deploy. There are instructions to set it up without docker as well.

126

A simple selfhosted URL shortener with no unnecessary features. Simplicity and speed are the main foci of this project. The docker image is ~6 MB (compressed), and it uses <5 MB of RAM under regular use.

view more: next ›

SinTan1729

joined 3 months ago