3 ms·

I'm all for self-hosting like this or using less known services. But what about discoverability? Is there any good search engine for code? These days I often f

I'm all for self-hosting like this or using less known services. But what about discoverability? Is there any good search engine for code? These days I often find more interesting projects when searching code on GH rather than by name or description on repos.

rootnod3 1y ago
There's a project idea.
torium 1y ago
> I'm all for self-hosting like this or using less known services. I'm all for the idea of self-hosting in abstract, but in practice I don't want to spend my life looking after services. I'm all for the idea of growing your own rice, but in practice I'd rather pay someone else to do it for me. I'm not trolling, I'm just emphasizing a super super important aspect which HNers tend to minimize, which is that self-hosting is work and even people who are technically able to do it might not want to.
- wpm 1y ago
  Past the initial setup, really there's not much to look after outside of the odd issue here and there which can usually just be a "go restart container" solution.
- blueflow 1y ago
  I think its like 3 years that i put the upgrade commands into a cronjob and stopped looking after the server. It hasn't broken so far & is up-to-date. I think it only works with dumb and simple software stacks, though.
- nine_k 1y ago
  I suppose that the TFA author is lowering their load by not having to respond to inane issues, which is also work. Otherwise, yes, non-essential things are best delegated, especially when it's free. Some essential things also have to be delegated, if doing them yourself takes too much (like growing rice). The latter works best when the essential thing is a commodity with a wide choice of suppliers (like rice).
- uncircle 1y ago
  In the age of Docker & co., people really overestimate how much effort it is to self-host a service. Probably it’s the entire generation that never ventured outside using AWS managed services. In practice, if you do not require 99.99% uptime SLAs, all you do is connect every 6 months to do a docker pull and update the image.
dboreham 1y ago
You can setup mirroring to a github repo, with a repo description "This is a read-only mirror of <other non-github repo>". People find the project on GitHub and from there are directed to your self-hosted Gitea/Gitlab etc.

rootnod3 1y ago

There's a project idea.

torium 1y ago

> I'm all for self-hosting like this or using less known services. I'm all for the idea of self-hosting in abstract, but in practice I don't want to spend my life looking after services. I'm all for the idea of growing your own rice, but in practice I'd rather pay someone else to do it for me. I'm not trolling, I'm just emphasizing a super super important aspect which HNers tend to minimize, which is that self-hosting is work and even people who are technically able to do it might not want to.

wpm 1y ago
Past the initial setup, really there's not much to look after outside of the odd issue here and there which can usually just be a "go restart container" solution.
blueflow 1y ago
I think its like 3 years that i put the upgrade commands into a cronjob and stopped looking after the server. It hasn't broken so far & is up-to-date. I think it only works with dumb and simple software stacks, though.
nine_k 1y ago
I suppose that the TFA author is lowering their load by not having to respond to inane issues, which is also work. Otherwise, yes, non-essential things are best delegated, especially when it's free. Some essential things also have to be delegated, if doing them yourself takes too much (like growing rice). The latter works best when the essential thing is a commodity with a wide choice of suppliers (like rice).
uncircle 1y ago
In the age of Docker & co., people really overestimate how much effort it is to self-host a service. Probably it’s the entire generation that never ventured outside using AWS managed services. In practice, if you do not require 99.99% uptime SLAs, all you do is connect every 6 months to do a docker pull and update the image.

dboreham 1y ago

You can setup mirroring to a github repo, with a repo description "This is a read-only mirror of <other non-github repo>". People find the project on GitHub and from there are directed to your self-hosted Gitea/Gitlab etc.