4 ms·
Why not use the AGPL version? (Announcement for those who haven’t seen it: https://goteleport.com/blog/teleport-community-license/ https://goteleport.com/blog/
by cpach 2y ago
Why not use the AGPL version?
(Announcement for those who haven’t seen it: https://goteleport.com/blog/teleport-community-license/ https://goteleport.com/blog/teleport-community-license/)
- tmottabr 2y agoBecause the community edition is no longer AGPL and no longer being developed and the new license has this clause: Companies may use Teleport Community Edition on the condition they have less than 100 employees and less than $10MM in annual revenue (AR). Like op said in his post..
- cpach 2y agoThis repo still has AGPL… and another license… Not sure if AGPL covers all areas of the codebase? https://github.com/gravitational/teleport https://github.com/gravitational/teleport
- tmottabr 2y agoyes, but new versions are no longer AGPL.. You could fork the last AGPL version but you would miss on new developments and fixes made after the license was changed.. Or you would have to work the re-develop everything from scratch..
- speedgoose 2y agoThat's a good point. Compiling and distributing binaries for all users and systems doesn't sound trivial. Only taking care of the teleport `tsh` client between windows, mac, and linux, for arm64 and amd64, sounds like a lot of boring work. Add that some users will likely download the forbidden tsh binary, that may call home and bring some unexpected bills, à la Oracle or Mirantis, it's not very appealing.
- clvx 2y agothey ship a flake.nix and a devbox.json configuration. Unless stuff is missing, this should be portable to produce the required binaries for linux/mac you need. This seems to produce typescript and golang.