starshipwinepineapple @ starshipwinepineapple @programming.dev

Posts

2

Comments

138

Joined

1 yr. ago

Sounds like you got it sorted but heres what i do:

• setup new repo in codeberg but don't check the box to initialize the repo
• for existing project, use git remote -v to verify your remotes. Update as necessary (git remote set-url [remote] [url]). If it's a new project you can just git init and add your remote.
• first push you'll need to specify the remote such as git push origin and after that you'll be fine to use just git push

This is what i do via acme.sh with the letsencrypt DNS-01 challenge. I have a cron job scheduled to renew/deploy

I use a bare git repo. After the initial set-up its just the basic git commands but invoked with a gitdf alias. I wrote a (non-monetized) blog post here about it.

If still needing a tui you could write a simple helper script to call the commands.

Thanks, I'll take a look!

Out of curiosity what wiki are you hosting? I have a community that we were thinking about moving our docs to a wiki to be more accessible to non tech savvy people wanting to contribute

Well you're in self-hosting so if you don't know docker yet, you'll get the advantage of learning it. It will open up many self hosting opportunities.

For me one advantage is just one central place for all my containers. I don't know how the package center handles storage but the docker version you'd have clear and easy access to the storage mount and would be able to make backups before big migrations, and you could set it up on a new server in the future. Imo there's just no reason to use the package center one unless youre not very tech savvy and don't want to learn anything else related to self hosting. I'm just assuming package center is easier in that regard but again i haven't used it.

Also, when there are critical CVEs like the nextjs one found this past week allowing RCE then yeah, you want your stuff as up to date as possible. You don't want to have to wait an unknown number of days for a downstream version to get updated. Docker let's you get your updates straight from the source

Fair enough, i mostly use symfonium so same thing since both jellyfin/navidrome support subsonic API. I do like using the navidrome web ui on PC though

I haven't gotten to hosting my own wiki, but i do host an internal-only personal knowledge static site built with hugo. I have it set to build the site on my server which then serves it. Very useful to have something like that or a wiki.

Nice! I haven't dug into the API yet. The big thing for me was actually pretty small feature but tandoor let's me scale recipes up and down on the fly with just a click of a button. I couldn't find that in Mealie. We do a lot of home cooking for guests and large parties so being able to quickly see the portions and scale a recipe up/down saves a lot of mental math or errors.

Edit: though looking at mealie demo again i see some recipes let you adjust the serving. But others do not.

Edit 2: seems to be related when ingredients aren't parsed

• media: jellyfin for videos, navidrome for music
• photos: immich
• game servers: +1 to foundryvtt if you're into tabletop rpgs. While the core software isn't open source, most systems are, and the pf2e system in particular is the best virtual tabletop experience you'll have on any platform.
• recipes: i settled on tandoor. Very much a fan of it.
• if you're a data nerd then chartdb for database diagraming, and cloudbeaver for database management

I much prefer navidrome for music over jellyfin. Better presentation and usage, tracks meaningful data and displays it by default, and won't delete your music library data if a folder gets moved. In other words jellyfin just gets rid of that data but navidrome will track missing songs and make you explicitly confirm removing them from the database.

I use wl-clipboard for wayland with another distro.

I didn't have "deeply rooted" projects, but i started by just creating new projects on codeberg. It gave me time to test it out before i moved the rest of my projects which i did ~6 months later.

For your use case i would consider the same. Figure out where you might like to migrate to and give it a test run with new projects. Then decide if you want to migrate the deeply rooted project(s) or not.

I didn't have to worry about the community much, both because i didn't have large projects and also because i was on gitlab to begin with. If anything going from gitlab to codeberg i had the same if not more engagement with my small projects. But my motivation for my migration was just wanting to use services that support what i support. For me that's what was most important in the long run.

Also re: github container registry. Forgejo (what codeberg uses) supports this: https://forgejo.org/docs/latest/user/packages/container/ . These images would then also show up on your project page under "packages" tab if it has been enabled

I have mine only internal so i haven't ran into that. But check console. You mention mobile so if you're on android you can hook it up to your pc and use debugging through chrome.. In the past I've had success looking at error messages to see why my requests were failing. Usually because i wasn't passing headers correctly.

I use symfonium and it looks like it let's you pass custom headers if needed. Good luck

Less about customizations and more just it doing what i want, and not doing things i don't want. When you build it all from the ground up then you don't have surpise bloat or walls to work around/within.

But most of my customizing from what people use probably would be around my dev environments. Things like rebuilding python libraries to support my gpu are fairly trivial in arch when i need to deviate from releases available through package managers (aur/pypi). Another thing was setting up my data science environments to share some core libraries but venv the rest.

It's a hard question to answer though because fundamentally I'm just using the computer how i want to use it. When you say customization it sounds like you are expecting me to do things differently than other people and really it's just like i said earlier-- doing things i want it to do, and not doing things i don't want it to do. And I'm not really sure what walls other people are stuck behind for me to know what I'm doing differently. I just find a problem, fix it, and move on

For me it mostly just came down to years of frustration combating windows to do what i wanted. Arch offers the level of control for me to set things up the way i like them. Was it harder to set up initially than another distribution? Yeah. But it was a worthwhile trade off

Neat project! And welcome to lemmy!

(Not mint)* On arch i used the arch install script, selected the nvidia drivers, and it just worked. I did have to spend some time making sure sure my nvidia gpu was my primary gpu and not my integrated graphics (cpu), but that was the biggest hurdle

That #1 is crucial. I see a lot of people get stuck in tutorial hell or burn out from doing other people's projects. Some tutorials are okay if you're just starting out but at some point switching to your own projects and challenging yourself is necessary

And since OP mentioned being on/off, i would also just say be consistent. Dedicate some time to work on your own projects so you're not forgetting stuff before it really sticks