5 ms·

Another Github alternative: http://phabricator.org/ http://phabricator.org/, better than GitLab, even. Self-hosted WebRTC audio/video conferencing: https://git

by _yy 11y ago

Another Github alternative: http://phabricator.org/ http://phabricator.org/, better than GitLab, even. Self-hosted WebRTC audio/video conferencing: https://github.com/jitsi/jitsi-meet https://github.com/jitsi/jitsi-meet

sytse 11y ago
Phabricator has some really neat features, which of those make it better than our GitLab for you?
- favadi 11y ago
  Its official installer doesn't contain a 3 web servers, 1 CI server and 1 chat server?
  - sytse 11y ago
    :) Thanks for your response. For other people some context, the GitLab Omnibus packages contains one web server (nginx, but you can also use it with Apache). The CI server is now integrated in GitLab itself (no longer a separate app). And you have the option to run Mattermost (but if you choose not to set this up it will not consume any ram or CPU). The Omnibus packages allow you to quickly install GitLab without having to do a lot of setup. The installation from source is also official, see https://about.gitlab.com/installation/ https://about.gitlab.com/installation/
    - antsar 11y ago
      Just wanted to +1 the parent comment. I'm sure you're tired of hearing this, but it feels pretty backwards that we have to disable parts of the installation just to get it to work alongside other stuff (with a shared nginx instance, etc). Its understandable why you wanted to bundle everything, and I bet it makes installation much easier for beginners and/or lazy sysadmins. That said, it would be even better if the installation worked with existing software instead of installing its own copy of everything. It seems like apt package dependencies would be more elegant than bundling everything together. Its great to have the installation from source as a supported option. But lets be honest, that's a world of pain that's simply unnecessary for a standard deployment. - A happy GitLab user
      - sytse 11y ago
        "It seems like apt package dependencies would be more elegant than bundling everything together." totally agree, that why is why we're sponsoring Pirate Praveen who is working on a native Debian package.
        favadi 11y ago
        That's great! Is there any ETA or discussion I can follow?
        sytse 11y ago
        The feedback issue is in http://feedback.gitlab.com/forums/176466-general/suggestions/6151718-native-debian-deb-and-fedora-rpm-packages http://feedback.gitlab.com/forums/176466-general/suggestions... but Pirate Praveen mostly sends updates by email and the GitLab issue tracker. He has it running and seems to be in the final stages.
        sytse 11y ago
        I learned that the task tracker for this is at https://gitlab.com/debian-ruby/TaskTracker/milestones/1 https://gitlab.com/debian-ruby/TaskTracker/milestones/1

by _yy 11y ago

sytse 11y ago

Phabricator has some really neat features, which of those make it better than our GitLab for you?

favadi 11y ago
Its official installer doesn't contain a 3 web servers, 1 CI server and 1 chat server?
- sytse 11y ago
  :) Thanks for your response. For other people some context, the GitLab Omnibus packages contains one web server (nginx, but you can also use it with Apache). The CI server is now integrated in GitLab itself (no longer a separate app). And you have the option to run Mattermost (but if you choose not to set this up it will not consume any ram or CPU). The Omnibus packages allow you to quickly install GitLab without having to do a lot of setup. The installation from source is also official, see https://about.gitlab.com/installation/ https://about.gitlab.com/installation/
  - antsar 11y ago
    Just wanted to +1 the parent comment. I'm sure you're tired of hearing this, but it feels pretty backwards that we have to disable parts of the installation just to get it to work alongside other stuff (with a shared nginx instance, etc). Its understandable why you wanted to bundle everything, and I bet it makes installation much easier for beginners and/or lazy sysadmins. That said, it would be even better if the installation worked with existing software instead of installing its own copy of everything. It seems like apt package dependencies would be more elegant than bundling everything together. Its great to have the installation from source as a supported option. But lets be honest, that's a world of pain that's simply unnecessary for a standard deployment. - A happy GitLab user
    - sytse 11y ago
      "It seems like apt package dependencies would be more elegant than bundling everything together." totally agree, that why is why we're sponsoring Pirate Praveen who is working on a native Debian package.
      - favadi 11y ago
        That's great! Is there any ETA or discussion I can follow?
        sytse 11y ago
        The feedback issue is in http://feedback.gitlab.com/forums/176466-general/suggestions/6151718-native-debian-deb-and-fedora-rpm-packages http://feedback.gitlab.com/forums/176466-general/suggestions... but Pirate Praveen mostly sends updates by email and the GitLab issue tracker. He has it running and seems to be in the final stages.
        sytse 11y ago
        I learned that the task tracker for this is at https://gitlab.com/debian-ruby/TaskTracker/milestones/1 https://gitlab.com/debian-ruby/TaskTracker/milestones/1