Gitbucket VS swiper

Gitbucket (https://gitbucket.github.io/)

GitBucket

Link: https://github.com/gitbucket/gitbucket

Another self-hosted project in the space that i've seen was GitBucket, although it runs on the JVM (not necessarily a bad thing, just different from Go): https://gitbucket.github.io/

Version control Systems eg. Github, Bitbucket, Gitbucket help in version control of your code and generally storage of your code. It can also serve as a visual reminder of the progress you make eg. on Github there is a monitoring system that shows how many days you are active on the platform.

> Git itself decentralizes source control, and yet we all want to use single-point-of-failure Github.

This is pretty much why both the organization that i work for, as well as i personally for my homelab use self-hosted GitLab instances: https://about.gitlab.com/

Though in practice there are a lot of other options out there, like Gitea (https://gitea.com/) and GitBucket (https://gitbucket.github.io/), though maybe less so for alternative source control systems (e.g. SVN has been all forgotten, however that's a personal pet peeve).

Not only that, but i also utilize my own Sonatype Nexus (https://www.sonatype.com/products/repository-oss?topnav=true) instances to great success: for doing everything from mirroring container images that i need from DockerHub (e.g. due to their proposed removal policies for old images and already adopted rate limits), to mirroring Maven/npm/NuGet/pip/Ruby and other dependencies, so i don't have to connect to things on the Internet whenever i want to do a new build.

That not only improves resiliency against things on the Internet going down (apart from situations where i need something new and it's not yet cached), but also improves performance a lot in practice, when only the company servers need to be hit, or my own personal servers in the data center for my cloud hosted stuff, or my own personal servers in my homelab for my own stuff.

Admittedly, all of that takes a bit of setup, especially if you happen to expose anything to the web in a zero trust fashion (permissible for my own stuff, as long as i'm okay with manually managing CVEs just to probably get hacked in the end anyways, but definitely not that any corporation with an internal network would want to do), but in my eyes that's still worth the effort, if you value being in control of your own software stack and the ecosystem around it.

It's probably much less worth it, if you don't see that as a benefit and don't want to be the one responsible for whatever project you're working on getting hacked, e.g. if you'd fail to patch out the recent GitLab CVE where exiftools could execute arbitrary code, which is probably the case if you don't have the resources to constantly throw at maintenance, in comparison to companies with 100x - 1000x more resources than you have for that sort of stuff.

> Rails doesn't scale? Github's the largest code repository site in the world.

You know, i think i understand both of the viewpoints here. Personally, i'd say that Rails doesn't scale as well as i'd expect it to. You can definitely build scalable systems in it, though you'll end up throwing a whole bunch of hardware resources, when compared to certain other languages and technology stacks, to serve similar load.

For example, right now i self-host a GitLab (https://about.gitlab.com/) instance for managing my code repositories, CI builds and so on. Even with just me using it (alongside some automated processes), it routinely eats up close to 4 GB of RAM, which in my case is an entire VPSes worth and costs me about 60 Euros a year with Time4VPS (affiliate link, if you'd like to check it out: https://www.time4vps.com/?affid=5294) but would cost me way more in AWS, GCP etc. One could argue that that's not too expensive, but not everyone earns a lot of money and running 10-20 VPSes does eventually build up, since i can't afford colocation and my residential homelab setup with a WireGuard tunnel to bypass ISP NAT with a proxy VPS is pretty slow, even if i can afford more storage, RAM and CPU power that way.

Compare that situation to projects like Gogs (https://gogs.io/), Gitea (https://gitea.com/), GitBucket (https://gitbucket.github.io/) and sourcehut (https://sourcehut.org/) - i'd argue that all of them on average use less CPU resources and memory for accomplishing similar tasks. For example, have a look here: https://forgeperf.org/

However, we cannot ignore the fact that using Ruby might have been exactly what allowed for quickly creating the functionality of GitLab and many other platforms and tools out there, GitHub included, so the choice between usable software and innovation in the near future and performant software possibly years from now is a tricky one.

There are probably good arguments for both, but noone can declare either to be better. Personally, i don't mind using Ruby, Python or even PHP when it makes sense and i don't need to worry about scalability from day 0.

I saw this on HN and have been using it for the past two weeks for some small hobby projects. The docs are so-so but I got it set up in Docker without much hassle. I've since migrated completely from gitbucket. Great software - I encourage everyone to try it out.

A Git platform (like github or gitlab) written in Scala. Definitely not a pet project so might be fun to read the code. https://github.com/gitbucket/gitbucket

This is a good improvement. Personally though I left isearch behind. For further search convenience / functionality I highly recommend swiper.

Next you "only" have to remember (elisp) function names. "Completion UIs" like ivy/counsel, icomplete, helm or vertico/consult, give you a nice auto completion list on M-x (choose the one of them, you like the most). Some of those Completion UIs will display existing keybindings and a short documentation for commands, near the auto complete candidates. So you will start to remember more keybindings without "learning sessions", just because invoking functions via keybindings is much faster (more convenient).

Proposal 4 (group-function). This one is an actual addition, which allows candidate gouping in the style of Helm. Note that it is a pure addition. Completion UIs and completion packages work perfectly fine without it. It wouldn't be difficult to add support to Ivy. I wrote the patch.

For the unfamiliar, Swiper is a part of Ivy which lets you search through your buffer with a preview of match candidates: you type some text you're looking for, and up pops a list of matching lines in the minibuffer that you can then use the arrow keys, C-n C-p etc. to scroll through and select the one you want.

When I started using Emacs I was following the setup outlined by System Crafters, which I still think is a really good introduction. But, over the last few months I've started to replace packages with more "minimalist" or "stripped down" packages. I've switched from Ivy and Counsel to Vertico and Consult, and recently I switched from company to corfu for auto-completion.

Ah, neat. I hadn't considered appending comments for searchability. I'm currently getting searchabiity from M-x dwim-... and ivy completion.

Great question. I have one big file with a few hundreds book and quotations from them. Problem is with newlines. When I copy text from kindle it doesn't have newlines because it's depends on font size. So every quotation from book is on one line - could be few thousands chars. I use visual-line-mode and there is a big problem with that. Like swiper would just freeze your emacs if you try to search. https://github.com/abo-abo/swiper/issues/925 Anyone have same problem?

Then hit C-' (that's apostrophe, left of enter on US keyboards). Preferably with something like [ivy][https://github.com/abo-abo/swiper] set up so you can see what it's trying to autocomplete for you- it should be suggesting all of your org 'notebooks' in the targeted folder, as well as any buffers you have open.