When I said “hard limit” I was thinking of what the code enforces, and I remembered wrong, it’s 30 days. Whoops. I’ve used a week as the time period for merging duped stories/hot takes so big news doesn’t take over the homepage.
Thanks for the clarification! I’m usually not that quick to flag submissions as “already posted” but now I know there’s an informal limit I can make more informed choices.
Drew DeVault does your comment from last year that you’re opposed to officially supporting Docker deployment of sourcehut stand? I have a homelab where I like to mess with stuff and sourcehut’s Mercurial support looks really nice, but the install steps are daunting. I assume it wouldn’t actually be too bad, but when compared to something like Gitea’s declarative deployment via Docker which took me 3 seconds to start playing with, I hesitate. Either way thanks for working on sourcehut!
Yes, it stands. What also stands is the idea that if someone were to take on the role of building a third-party docker deployment for sourcehut, they would find the task reasonably easy to accomplish and I would be supportive of them, albeit insistent that it remain a third-party solution.
Note, however, that deploying sourcehut on docker is itself not the matter discussed in the linked ticket. As for the subject of the ticket, I still have no desire to address this at this time.
Reasonable stance! Perhaps I will attempt to tackle it some time (if no one else beats me to it).
I actually don’t even understand that ticket but it came up in a google search result for “sourcehut docker.” GPU passthrough with Docker? So confused.
I really like this, I just can’t go to an email-based workflow. It’s not just that I find it difficult, but I’d never be able to convince everyone I collaborate with to do it. I think Drew said at some point that he would consider web-based code review, any updates on that?
It’s a work in progress, but I still insist that people give it a fair shake, especially after writing resources like git-send-email.io to make it as painless as possible. Lately I also find it prudent to remind people that their development mail client needn’t be their only mail client.
One of those weird git hosting sites that don’t put code first. And that file browser’s is really bad. Who sorts files and directories alphabetically? Usually you put directories first.
And that file browser’s is really bad. Who sorts files and directories alphabetically?
I feel this isn’t totally fair. There’s a big red box on the front page that makes it quite clear that it’s early days for development:
Achtung! Sourcehut is still under heavy development, and while many of the services are usable, expect to find lots of missing polish, broken links, incomplete docs, and so on. Here be dragons!
It’s been on this site before, but it wasn’t caught by the duplicate link checker because the domain changed: https://lobste.rs/s/u4imgn/sr_ht_is_now_sourcehut
It’s been long enough a repost is OK. The hard limit is a week.
Gosh, do you really want to allow slightly-older-than-1-week material to be reposted here?
When I said “hard limit” I was thinking of what the code enforces, and I remembered wrong, it’s 30 days. Whoops. I’ve used a week as the time period for merging duped stories/hot takes so big news doesn’t take over the homepage.
Wow, that list of articles. That is certainly a powerful case for why the feature needs to exist.
Thanks for the clarification! I’m usually not that quick to flag submissions as “already posted” but now I know there’s an informal limit I can make more informed choices.
Oops! Thanks for letting us know!
Drew DeVault does your comment from last year that you’re opposed to officially supporting Docker deployment of sourcehut stand? I have a homelab where I like to mess with stuff and sourcehut’s Mercurial support looks really nice, but the install steps are daunting. I assume it wouldn’t actually be too bad, but when compared to something like Gitea’s declarative deployment via Docker which took me 3 seconds to start playing with, I hesitate. Either way thanks for working on sourcehut!
p.s. how do you @-mention a user on here?
Yes, it stands. What also stands is the idea that if someone were to take on the role of building a third-party docker deployment for sourcehut, they would find the task reasonably easy to accomplish and I would be supportive of them, albeit insistent that it remain a third-party solution.
Note, however, that deploying sourcehut on docker is itself not the matter discussed in the linked ticket. As for the subject of the ticket, I still have no desire to address this at this time.
Reasonable stance! Perhaps I will attempt to tackle it some time (if no one else beats me to it).
I actually don’t even understand that ticket but it came up in a google search result for “sourcehut docker.” GPU passthrough with Docker? So confused.
It’s for the CI service.
@altano you just type @ in front of the username and the markdown formatting does the rest
You just prepend
@to the username: @altanoI stumbled across this recently. Claims to support testing on BSDs, which may make it a suitable travis-a-like substitute for BSD folk.
Yes, it’s really cool, Drew DeVault here made it~!
I have been using SourceHut for git and NixOS CI, and it is really awesome. Consider subscribing!
I really like this, I just can’t go to an email-based workflow. It’s not just that I find it difficult, but I’d never be able to convince everyone I collaborate with to do it. I think Drew said at some point that he would consider web-based code review, any updates on that?
It’s a work in progress, but I still insist that people give it a fair shake, especially after writing resources like git-send-email.io to make it as painless as possible. Lately I also find it prudent to remind people that their development mail client needn’t be their only mail client.
One of those weird git hosting sites that don’t put code first. And that file browser’s is really bad. Who sorts files and directories alphabetically? Usually you put directories first.
I feel this isn’t totally fair. There’s a big red box on the front page that makes it quite clear that it’s early days for development:
Why don’t you submit an issue?
Fair to who? Its just obvious flaws.
I don’t really care.