Traveling Ruby VS Gitlab CI

If you absolutely need a native binary distribution for your apps, there is a project called Traveling Ruby that originated at Phusion, makers of the popular Phusion Passenger Ruby application server. It's worth noting that this project has a number of open issues that are aging and the latest commits are from 2021, so I'm not sure about its current status. There are also important caveats with regard to native extensions and Windows. Given the popularity of packages that require native extensions (like the XML/HTML library Nokogiri), you may find that this solution simply doesn't work for you.

You may be to get a precompiled binary with OpenSSL 1.1 statically linked. Maybe Traveling Ruby? https://github.com/phusion/traveling-ruby

There's really not much else in this space. The main alternative - Traveling Ruby - has limitations on Windows and I don't think it supports Ruby 3.0.

But even with all of the above, you're absolutely right, it is just easier to ship a binary blob. That's where the rewrite totally pays off. I just wonder whether the team has stressed all the options when it comes to keep ruby. There are packaging solutions which ship with its own interpreter, such as Travelling Ruby. And mruby could also generate a binary blob, although they'd have to open another can of works, such as finding replacements for dependencies such as net-ssh, which AFAIK can't be used with mruby. So in the end, maybe they did. And given the prevalence of go products in hashicorp, maybe it makes sense to just invest a bit more in it?

You could try using Traveling Ruby as an alternative to Ocra. I have only used Ocra in the past for this task, but I'd say it's worth a try.

## https://github.com/gitlabhq/gitlabhq/issues/694

// https://github.com/gitlabhq/gitlabhq/blob/e6d048d769240760008f0dbb6b811e1ebc675292/app/assets/javascripts/ide/components/repo_tab.vue#L3 import { GlIcon, GlTab } from '@gitlab/ui'; import { mapActions, mapGetters } from 'vuex'; import { __, sprintf } from '~/locale'; import ChangedFileIcon from '~/vue_shared/components/changed_file_icon.vue'; import FileIcon from '~/vue_shared/components/file_icon.vue'; import FileStatusIcon from './repo_file_status_icon.vue'; export default { components: { FileStatusIcon, FileIcon, GlIcon, ChangedFileIcon, GlTab, }, props: { tab: { type: Object, required: true, }, }, data() { return { tabMouseOver: false, }; }, computed: { ...mapGetters(['getUrlForPath']), closeLabel() { if (this.fileHasChanged) { return sprintf(__('%{tabname} changed'), { tabname: this.tab.name }); } return sprintf(__('Close %{tabname}'), { tabname: this.tab.name }); }, showChangedIcon() { if (this.tab.pending) return true; return this.fileHasChanged ? !this.tabMouseOver : false; }, fileHasChanged() { return this.tab.changed || this.tab.tempFile || this.tab.staged || this.tab.deleted; }, }, methods: { ...mapActions(['closeFile', 'updateDelayViewerUpdated', 'openPendingTab']), clickFile(tab) { if (tab.active) return; this.updateDelayViewerUpdated(true); if (tab.pending) { this.openPendingTab({ file: tab, keyPrefix: tab.staged ? 'staged' : 'unstaged' }); } else { this.$router.push(this.getUrlForPath(tab.path)); } }, mouseOverTab() { if (this.fileHasChanged) { this.tabMouseOver = true; } }, mouseOutTab() { if (this.fileHasChanged) { this.tabMouseOver = false; } }, }, };

In setting this up, I have followed the gitlab setup guide and the passenger documentation.

Do you know G2 awards 4.4 stars to both GitLab & CircleCI? Just like GitHub stars, StackShares stack counts reflect the popularity of technology. CircleCI boasts around 7.4k stacks, while GitLab enjoys 31.1k stacks. Besides, GitLab as well as GitLab CI are open-source technologies and have garnered 22k+ stars on GitHub. Wait, this is not a reflection of how good GitLab is at CI/CD. These numbers reflect overall popularity. CircleCI is primarily “a niche-focused continuous integration tool” while GitLab wears multiple hats, including “version control & code collaborator.”