They both also have cloud options, one focussing more on large scale and features I don’t care about, the other others some sort of hosted instance that’s private.
Sorry, doesn’t help me
71 karma · joined January 1, 2021
They both also have cloud options, one focussing more on large scale and features I don’t care about, the other others some sort of hosted instance that’s private.
Sorry, doesn’t help me
That said, looking at recent releases, there are nice things from both, and if I wasn’t running GHES, I’d be stuck to choose between the two
I have a 1U (or more), sitting in a rack in a local datacenter. I have an IP block to myself.
Those servers are now publicly exposed and only a few ports are exposed for mail, HTTP traffic and SSH (for Git).
I guess my use case also changes in that I don’t use things just for me to consume, select others can consume services I host.
My definition here of self-hosting isn’t that I and I only can access my services; that’s be me having a server at home which has some non critical things on it.
When I was a manager at Amazon, I asked my engineers to keep a list of what they were proud of throughout the year, as it’d be used in annual and mid year reviews..
They offered Plane One for about a year and but for $799 ish, then killed it in March this year, with the only options now subscription only.
I do feel that Grafana are slowly becoming more cloud-first, regardless of that a lot of work is done in OSS. Even if I look at the blog, most content there is about Grafana Cloud. The "Grafana LGTM Stack news" section isn't navigable.
With Opsgenie shutting down, and I see that DataDog releasing their on-call feature; maybe migrating away from the LGTM solution might be a whole thing if there's nothing to replace OnCall; not that it would be easy, mind you.
Those damned earthquakes destroying different equipment (usually the slack tongue slicer) annoy me, but it’s all good fun though.
I tried to play the reboot, but I prefer Theme Hospital.
On the mend.mid is my favourite piece of music from the series.
I am an engineering manager with experience in building and operating cloud services. My prior work was as an SRE, thus have a solid understanding of end-to-end engineering principles.
Security is lax at most companies but even having worked as an engineer on support rotation, customer anc production access was the last thing I could do and I needed to have exhausted all other options. I don’t feel retaining production access to generate tokens should be a thing.
The majority of react sites nowadays are just NextJS. It might be that the future of react based applications isn’t react, but nextjs.
When things don’t work on Linux, the last thing I want to do is open the terminal.
Routing domains to a container shouldn’t be significantly different to doing it in production.
Creating standards would be better, but in the lack of, a closely tied CI/CD or runner or whatever would be sufficient.
Right now, even the Gitea/Gogs/Forgejo ecosystem is fragmented. The latter fork exists, but I don't see how it's different from Foregjo and I have no inclination to believe that it will be optimised for codeberg's use case beyond others, but now I do ask - if Gitea implements functionality such as CICD / run pipelines, will Forgejo keep that or strip it out of their fork, if they maintain upstream syncs?
Is there even a document about what the product aims are? If they're just going to maintain Gitea sync without adding functionality, why should I even look at it, which is likely to fall out of sync with Gitea?