Live data from Hacker News

Atlassian prepares to abandon on-prem server products

theregister.com

191–200 of 205 posts

Re: Atlassian prepares to abandon on-prem server products

#191
post #103
post #75

Earlier quoted context omitted.

Not speaking for the GP. I use MkDocs and keep my personal notes. The only weak spot for me is that I haven't fully grokked search and as my notes grow, it can be harder to find things. I alternate between figuring out how search and how to bolt on some other search utility. MkDocs includes a utility to publish to Github pages but I keep my notes on a self hosted Gitea server and serve using "python -m http".

Is this a fully collaborative tooling with self linking? Having hundreds of out of date, and insecure word documents is a dismal affair when you get a call in the middle of the night. For issue resolution, documents steps are moving right in to the ticketing system for linkage to incidents. That’s fine. For general documentation though. It doesn’t belong in the ticketing system and what a pain in my ass.

If I understand your question, it's a lot simpler than that. (Simpler as in not that functional.) It represents the directory structure as cascading menus.

I edit using VS Code and it provides help with linking from one document to another, including navigating to the file and even linking second level ('##') headings. MkDocs can report broken links when it builds the site.

Collaboration could be through sharing a Git repo. Perhaps other other ways I can't think of at this moment. Any way you could collaborate editing text files should work.

Re: Atlassian prepares to abandon on-prem server products

#192
We just chatted with Atlassian and just installed a pretty large on-prem env. (mandatory to meet restrictions), and think this title is misleading in that you can still buy supported on-prem server products, with support licenses. Will the focus of dev. be for their cloud products? 100% - TBH who isn't doing this now-adays (cough MSFT etc.)

RANT: This force to cloud is total BS though and the S*T that Postman just pulled reinforces my general disdain for 'forced' cloud. Hopefully comps. will realize this and fill this spot in the market. RANTOFF

Re: Atlassian prepares to abandon on-prem server products

#193

Earlier quoted context omitted.

Sure. We're focusing first on converting everything to plain Markdown and using a Git repo to manage the content. Writers can use whatever Markdown tool they prefer for this. (I'm using Obsidian and others are iA Writer.) I have yet to decide on the docs publishing tool, but I'm testing Astro, Vitepress, and Markdoc for publishing. I'm leaning towards Astro since it's very flexible, easy to add small bits of interact…

You should take a look at foam. It's a toolchain for notes and such, similar to obsidian, but open source. It's main interface is a vscode plugin, but has HTML generators and such, as well as just being markdown, so you can use Pandoc or anything else to make HTML out of it

I wish people would link software they recommend, because it saves me a lot of confusion when they are semi obscure. I believe this is the software you are referring to? (I'm using obsidian but don't like that it's not opensource and don't like logseq, except for their journals feature so I'm actually quite interested in checking out foam) https://foambubble.github.io/foam/

Re: Atlassian prepares to abandon on-prem server products

#194

Earlier quoted context omitted.

Obsidian is a pretty good solution for this in my experience

Obsidian does not support collaboration. It's a fantastic tool but strictly singleplayer.

Obsidian has a feature called "Shared vaults" which teams use to collaborate. You can also use a shared Git repo, or other cloud/network storage (e.g. Dropbox)

https://help.obsidian.md/Obsidian+Sync/Share+remote+vaults

Re: Atlassian prepares to abandon on-prem server products

#195
post #151

We(as in everyone) are in a serious need of a new git server product. Just do git serving, and do it well. Preferably in a way multiple nodes can be run active-active for scaling and reliability. No need for cicd (Jenkins is fine for that, thank you very much). What are minimum viable features for me? Granular (per branch) security access. Integration with AD federation and other auth providers(congnito, aws iam) and…

> Jenkins is fine for that As someone who managed hundreds of Jenkins instances from 2016 to 2018, Jenkins is now complete crap, stop using it. It was an ok product when the open source world offered no alternative but it's completely outdated compared to today's solutions. Deploying it sucks, its config as code format(s) are awful, the plugins are shit, upgrades can (and do) break everything, and I won't even saying…

What alternative would you suggest?

None of the large companies I worked at used anything other than Jenkins for cicd (well in one place we did use azure devops server - back then called teams If I remember correctly, but that was just for one app development team).

Where they didn't use Jenkins they didn't have a dedicated cicd runner and they used github/gitlab instead. Both of these (although github less) suck for cicd IMO.

Re: Atlassian prepares to abandon on-prem server products

#196
post #151

Earlier quoted context omitted.

> Jenkins is fine for that As someone who managed hundreds of Jenkins instances from 2016 to 2018, Jenkins is now complete crap, stop using it. It was an ok product when the open source world offered no alternative but it's completely outdated compared to today's solutions. Deploying it sucks, its config as code format(s) are awful, the plugins are shit, upgrades can (and do) break everything, and I won't even saying…

What alternative would you suggest? None of the large companies I worked at used anything other than Jenkins for cicd (well in one place we did use azure devops server - back then called teams If I remember correctly, but that was just for one app development team). Where they didn't use Jenkins they didn't have a dedicated cicd runner and they used github/gitlab instead. Both of these (although github less) suck for…

Concourse, Drone, Gitlab CI all work fine. I've also heard of GoCD that looks interesting and looks like an actual "Jenkins successor" (more than an alternative IMO), but I've never used it.

Re: Atlassian prepares to abandon on-prem server products

#197
post #165

Earlier quoted context omitted.

Hi there! I lead the product teams for planning features at GitLab. Issues at the group level are in the works to meet this exact need. You can follow the work in this issue https://gitlab.com/groups/gitlab-org/-/epics/8308 . As always, would love to hear from you in the issue if you have feedback about the approach or have follow up questions.

Thanks for providing this info. I do use gitlab-ce at home for my personal projects and think it's awesome. I would recommend it to work in terms of its features for code management and build pipelines. But I just cannot see any of our product management team wanting to use this for Roadmap/Epic/Task tracking at all. Its far too technical and too close to the code, both of which are things they have neither the time,…

Hey `wdfx` GitLab team member here. :)

>[Roadmap/Epic/Task tracking] Its far too technical and too close to the code

I'm a Product Manager in the Plan stage at GitLab and I'd love to learn more about this impression. Would you be willing to share more either in thread or on a call?

Specially, I'm trying to understand what about the GitLab Plan tools (epics, roadmaps, etc) feel dev-centric?

Re: Atlassian prepares to abandon on-prem server products

#198

Earlier quoted context omitted.

You should take a look at foam. It's a toolchain for notes and such, similar to obsidian, but open source. It's main interface is a vscode plugin, but has HTML generators and such, as well as just being markdown, so you can use Pandoc or anything else to make HTML out of it

I wish people would link software they recommend, because it saves me a lot of confusion when they are semi obscure. I believe this is the software you are referring to? (I'm using obsidian but don't like that it's not opensource and don't like logseq, except for their journals feature so I'm actually quite interested in checking out foam) https://foambubble.github.io/foam/

Yeah that's it. Sorry for not linking it, I originally wrote that comment on mobile

Re: Atlassian prepares to abandon on-prem server products

#199

Earlier quoted context omitted.

Yes, I know and that's why I'm asking. I suspect many companies I know are on the "Server edition" and I'm curious how much more expensive it will get for them.

Oh I misunderstood, sorry about that. We went from Server -> Cloud -> GTFO. Server also had tiered pricing starting at $10 for 3 users. It went up from there in much saner increments but I don’t recall them. We exited the ecosystem at the last cloud price hike. Their product pricing people are delusional.

Thanks! I dug bit deeper and found old pricing tables. For Jira and the 500 to 1000 user tiers I'm interested in it was roughly about twice the money going from Server to Datacenter. Interestingly the Datacenter prices per user are similar to the cloud prices, so from Atlassian's perspective it is more a price adjustment with regard to the incongruous Server pricing. From the customer perspective it's still a bummer and I guest many will go straight to the GTFO tier.

Re: Atlassian prepares to abandon on-prem server products

#200
post #140
post #126

Earlier quoted context omitted.

Curious what you see as the "UNIX BS" in running a server? Is it the need to CLI? Or just the number of knobs that you can frob? Too many choices? Interested in how such a server system might look.

Almost total absence of GUIs and proper documentation. A big part of why people pay for AWS and friends is not instant scalability or even the fancy features, but simply because clouds wrap a half-way decent GUI around high level server oriented tasks combined with an actual task focused user guide. To compare, try comparing the docs and GUI help you get deploying a simple serverless app to Lambda+RDS vs configuring…

Thanks for sharing that.

I think the documentation aspect is often overlooked. Even RedHat's subscriber-only documentation is ... quite dense, and yet, not very deep.

Post reply on HN