7 ms·

Sourcegraph CEO here. We're back to work on testing release candidates for Sourcegraph 2.12, coming out this week. I'm especially excited about a few big new fe

by sqs 8y ago

Sourcegraph CEO here. We're back to work on testing release candidates for Sourcegraph 2.12, coming out this week. I'm especially excited about a few big new features that fit really nicely into the code search and browsing workflows people use Sourcegraph for: - https://github.com/sourcegraph/about/blob/master/projects/extension-authoring.md https://github.com/sourcegraph/about/blob/master/projects/ex... - https://github.com/sourcegraph/about/blob/master/projects/sourcegraph-for-gitlab.md https://github.com/sourcegraph/about/blob/master/projects/so... - https://about.sourcegraph.com/blog/discuss-code-and-docs-in-repositories/ https://about.sourcegraph.com/blog/discuss-code-and-docs-in-... along with a whole host of improvements to code search, code intelligence, self-hosted deployment on a single node and k8s, etc. Happy to answer any questions folks have about our open sourcing. I summarized the business case at https://twitter.com/sqs/status/1046913901688807424 https://twitter.com/sqs/status/1046913901688807424. And we went with the Apache License (2.0) and an open core model because that's about as standard and as open as possible for this kind of thing.

neves 8y ago
Is it easy to add new languages? I work at a large company with some very old codebases.
- beliu 8y ago
  @chrismwendt is a Sourcegrapher working on this. Posting this on his behalf: Here is how I added GraphQL support last week: - Follow the hello world tutorial https://github.com/sourcegraph/sourcegraph-extension-docs/blob/master/tutorials/hello-world.md https://github.com/sourcegraph/sourcegraph-extension-docs/bl... - Add logic to handle hovers and definitions https://github.com/sourcegraph/sourcegraph-graphql https://github.com/sourcegraph/sourcegraph-graphql - Write the server part https://github.com/chrismwendt/graphql-ws-langserver https://github.com/chrismwendt/graphql-ws-langserver (once a browser-based GraphQL analysis library exists, this would be unnecessary because the analysis could be done entirely in the browser) It's available at https://sourcegraph.com/extensions/chris/graphql https://sourcegraph.com/extensions/chris/graphql and once you enable it you can test it out on a GraphQL file such as https://sourcegraph.com/github.com/chrismwendt/graphql-ws-langserver@master/-/blob/schema.gql?diff=5a6f2dc350ec67e8aa8c8b606fd3a8fb0c66d578 https://sourcegraph.com/github.com/chrismwendt/graphql-ws-la... (it's pretty slow/janky at the moment and could be improved, but works). If you're interested in interfacing with other tools too, you might be interested in LSP (Language Server Protocol): - https://langserver.org/ https://langserver.org/ - https://microsoft.github.io/language-server-protocol/specification https://microsoft.github.io/language-server-protocol/specifi...
ntonozzi 8y ago
Congrats Quinn and company! I hope there's not too much of my code lurking in there =)
- slimsag 8y ago
  Oh! Hey Nico :) Hope all is going well! I miss having ya around!
brylie 8y ago
Cool! Are you working on IDE plygins, e.g. for Atom?
- sqs 8y ago
  Yes, we have basic editor/IDE plugins that let you (1) open up Sourcegraph to the current document's file/line and (2) search. Sourcegraph for Atom is in prelrease at https://github.com/sourcegraph/sourcegraph-atom https://github.com/sourcegraph/sourcegraph-atom. Other editors are at https://about.sourcegraph.com/docs/integrations/ https://about.sourcegraph.com/docs/integrations/. What features (other features, if any) are you specifically interested in? It would be awesome if you posted feature request issues on the open-source repos for sourcegraph/sourcegraph or for the editor plugins!
  - fredsanford 8y ago
    No vim/nvim or emacs editor plugins? The two most popular editors used by programmers... Sigh
    - kevinherron 8y ago
      Citation needed...
    - sqs 8y ago
      Sourcegraph CEO here. I use Emacs personally and configured https://github.com/sshaw/git-link https://github.com/sshaw/git-link to make it work for me. See https://github.com/sshaw/git-link#building-links-and-adding-services https://github.com/sshaw/git-link#building-links-and-adding-.... Will submit a PR or make our own sourcegraph-mode at some point (if anyone else wants to do so, that would be awesome).
sytse 8y ago
Thanks for creating Sourcegraph for GitLab https://github.com/sourcegraph/about/blob/master/projects/sourcegraph-for-gitlab.md https://github.com/sourcegraph/about/blob/master/projects/so... we really appreciate it. Every single developer that used Sourcegraph and talked to me about it loved the product. I think that every code product must have intelligent navigation. I saw you already responded to my tweet in https://twitter.com/sqs/status/1046986755919024129 https://twitter.com/sqs/status/1046986755919024129 We're looking forward to add Sourcegraph to GitLab by default and it is awesome that you offer to do the work. Thanks for choosing the Apache license which will make this much more acceptable to some companies then for example AGPL.
- sqs 8y ago
  Sourcegraph CEO here. :) Thanks for creating GitLab and for the kind words. We're indeed looking forward to adding Sourcegraph to GitLab by default. Look out for a prototype/proposal MR from us in a bit. That's one of the super valuable kinds of features/integrations that we can do now that Sourcegraph is open source!
  - sytse 8y ago
    Awesome! Apart from the Web IDE having Sourcegraph code navigation by default in the repository view would be great.
  - jramsay 8y ago
    Amazing! Here's an issue we can use to discuss: https://gitlab.com/gitlab-org/gitlab-ce/issues/41925 https://gitlab.com/gitlab-org/gitlab-ce/issues/41925
- mikepurvis 8y ago
  It's too bad that a browser extension is required to make this work. I've asked previously for GitLab to provide the necessary hooks so that any plugin could offer this type of functionality in a first class way, and was told that the proposal lacked a "concrete first need". I suppose SourceGraph has now demonstrated the usefulness of such a thing, which is great! Ref: https://gitlab.com/gitlab-org/gitlab-ce/issues/33047 https://gitlab.com/gitlab-org/gitlab-ce/issues/33047
regnerba 8y ago
Hey, couple questions for you: - We are a pretty small shop, only 3 developers, and looking at Sourcegraph for the first time. We have a full Kubernetes cluster for running some of our production applications and would be happy to run this there. The Sourcegraph site lists a Quickstart instructions and instructions for Data Center. I am unsure what exactly the difference between them is. - The Docker image for sourcegraph/server (used in your Quickstart instructions) doesn't have a Dockerfile listed anywhere. Is that available somewhere? - The Quickstart instructions also seem to instruct mounting the Docker socket into the container. I haven't seen anything that explains why that is required. Basically wondering which version I should be looking to deploy for our small team.
- slimsag 8y ago
  You should definitely use our Quickstart instructions :) You can deploy it to your existing Kubernetes cluster (or any other Docker environment). - The Quickstart instructions[1] describe how to set up a single-machine single-container Sourcegraph instance, which is recommended for small teams. Our Data Center[2] offering is for large teams and runs Sourcegraph across multiple machines in multiple containers for high availability, scalability, etc. - The Docker Hub image sourcegraph/server is the official, free Sourcegraph build is called Sourcegraph Core and it includes various paid enterprise features built in so that upgrading to Sourcegraph Enterprise is easy (you only need to supply a license key, rather than migrating to a new Docker image). So, the exact recipe for building it is not open-source. However, we use the same exact Dockerfile in Sourcegraph OSS[4] which you can take a look at. - Each language server providing code intelligence will run as separate Docker container. By mounting the Docker socket into the container, Sourcegraph can automatically start/stop/manage these containers for you. However, this is not required, and in the case of Kubernetes deployment we do not recommend it, please see the "Manual Installation" section of our Code Intelligence docs[5] for more information. [1] https://about.sourcegraph.com/docs https://about.sourcegraph.com/docs [2] https://github.com/sourcegraph/deploy-sourcegraph https://github.com/sourcegraph/deploy-sourcegraph [3] https://about.sourcegraph.com/pricing/ https://about.sourcegraph.com/pricing/ [4] https://github.com/sourcegraph/sourcegraph/blob/master/cmd/server/dockerfile.go https://github.com/sourcegraph/sourcegraph/blob/master/cmd/s... [5] https://about.sourcegraph.com/docs/code-intelligence/install https://about.sourcegraph.com/docs/code-intelligence/install
AsyncAwait 8y ago
Just wanted to say thanks for making code intelligence part of the core product, Sourcegraph has been wonderful!

by sqs 8y ago

neves 8y ago

Is it easy to add new languages? I work at a large company with some very old codebases.

beliu 8y ago
@chrismwendt is a Sourcegrapher working on this. Posting this on his behalf: Here is how I added GraphQL support last week: - Follow the hello world tutorial https://github.com/sourcegraph/sourcegraph-extension-docs/blob/master/tutorials/hello-world.md https://github.com/sourcegraph/sourcegraph-extension-docs/bl... - Add logic to handle hovers and definitions https://github.com/sourcegraph/sourcegraph-graphql https://github.com/sourcegraph/sourcegraph-graphql - Write the server part https://github.com/chrismwendt/graphql-ws-langserver https://github.com/chrismwendt/graphql-ws-langserver (once a browser-based GraphQL analysis library exists, this would be unnecessary because the analysis could be done entirely in the browser) It's available at https://sourcegraph.com/extensions/chris/graphql https://sourcegraph.com/extensions/chris/graphql and once you enable it you can test it out on a GraphQL file such as https://sourcegraph.com/github.com/chrismwendt/graphql-ws-langserver@master/-/blob/schema.gql?diff=5a6f2dc350ec67e8aa8c8b606fd3a8fb0c66d578 https://sourcegraph.com/github.com/chrismwendt/graphql-ws-la... (it's pretty slow/janky at the moment and could be improved, but works). If you're interested in interfacing with other tools too, you might be interested in LSP (Language Server Protocol): - https://langserver.org/ https://langserver.org/ - https://microsoft.github.io/language-server-protocol/specification https://microsoft.github.io/language-server-protocol/specifi...

ntonozzi 8y ago

Congrats Quinn and company! I hope there's not too much of my code lurking in there =)

slimsag 8y ago
Oh! Hey Nico :) Hope all is going well! I miss having ya around!

brylie 8y ago

Cool! Are you working on IDE plygins, e.g. for Atom?

sqs 8y ago
Yes, we have basic editor/IDE plugins that let you (1) open up Sourcegraph to the current document's file/line and (2) search. Sourcegraph for Atom is in prelrease at https://github.com/sourcegraph/sourcegraph-atom https://github.com/sourcegraph/sourcegraph-atom. Other editors are at https://about.sourcegraph.com/docs/integrations/ https://about.sourcegraph.com/docs/integrations/. What features (other features, if any) are you specifically interested in? It would be awesome if you posted feature request issues on the open-source repos for sourcegraph/sourcegraph or for the editor plugins!
- fredsanford 8y ago
  No vim/nvim or emacs editor plugins? The two most popular editors used by programmers... Sigh
  - kevinherron 8y ago
    Citation needed...
  - sqs 8y ago
    Sourcegraph CEO here. I use Emacs personally and configured https://github.com/sshaw/git-link https://github.com/sshaw/git-link to make it work for me. See https://github.com/sshaw/git-link#building-links-and-adding-services https://github.com/sshaw/git-link#building-links-and-adding-.... Will submit a PR or make our own sourcegraph-mode at some point (if anyone else wants to do so, that would be awesome).

sytse 8y ago

Thanks for creating Sourcegraph for GitLab https://github.com/sourcegraph/about/blob/master/projects/sourcegraph-for-gitlab.md https://github.com/sourcegraph/about/blob/master/projects/so... we really appreciate it. Every single developer that used Sourcegraph and talked to me about it loved the product. I think that every code product must have intelligent navigation. I saw you already responded to my tweet in https://twitter.com/sqs/status/1046986755919024129 https://twitter.com/sqs/status/1046986755919024129 We're looking forward to add Sourcegraph to GitLab by default and it is awesome that you offer to do the work. Thanks for choosing the Apache license which will make this much more acceptable to some companies then for example AGPL.

sqs 8y ago
Sourcegraph CEO here. :) Thanks for creating GitLab and for the kind words. We're indeed looking forward to adding Sourcegraph to GitLab by default. Look out for a prototype/proposal MR from us in a bit. That's one of the super valuable kinds of features/integrations that we can do now that Sourcegraph is open source!
- sytse 8y ago
  Awesome! Apart from the Web IDE having Sourcegraph code navigation by default in the repository view would be great.
- jramsay 8y ago
  Amazing! Here's an issue we can use to discuss: https://gitlab.com/gitlab-org/gitlab-ce/issues/41925 https://gitlab.com/gitlab-org/gitlab-ce/issues/41925
mikepurvis 8y ago
It's too bad that a browser extension is required to make this work. I've asked previously for GitLab to provide the necessary hooks so that any plugin could offer this type of functionality in a first class way, and was told that the proposal lacked a "concrete first need". I suppose SourceGraph has now demonstrated the usefulness of such a thing, which is great! Ref: https://gitlab.com/gitlab-org/gitlab-ce/issues/33047 https://gitlab.com/gitlab-org/gitlab-ce/issues/33047

regnerba 8y ago

Hey, couple questions for you: - We are a pretty small shop, only 3 developers, and looking at Sourcegraph for the first time. We have a full Kubernetes cluster for running some of our production applications and would be happy to run this there. The Sourcegraph site lists a Quickstart instructions and instructions for Data Center. I am unsure what exactly the difference between them is. - The Docker image for sourcegraph/server (used in your Quickstart instructions) doesn't have a Dockerfile listed anywhere. Is that available somewhere? - The Quickstart instructions also seem to instruct mounting the Docker socket into the container. I haven't seen anything that explains why that is required. Basically wondering which version I should be looking to deploy for our small team.

slimsag 8y ago
You should definitely use our Quickstart instructions :) You can deploy it to your existing Kubernetes cluster (or any other Docker environment). - The Quickstart instructions[1] describe how to set up a single-machine single-container Sourcegraph instance, which is recommended for small teams. Our Data Center[2] offering is for large teams and runs Sourcegraph across multiple machines in multiple containers for high availability, scalability, etc. - The Docker Hub image sourcegraph/server is the official, free Sourcegraph build is called Sourcegraph Core and it includes various paid enterprise features built in so that upgrading to Sourcegraph Enterprise is easy (you only need to supply a license key, rather than migrating to a new Docker image). So, the exact recipe for building it is not open-source. However, we use the same exact Dockerfile in Sourcegraph OSS[4] which you can take a look at. - Each language server providing code intelligence will run as separate Docker container. By mounting the Docker socket into the container, Sourcegraph can automatically start/stop/manage these containers for you. However, this is not required, and in the case of Kubernetes deployment we do not recommend it, please see the "Manual Installation" section of our Code Intelligence docs[5] for more information. [1] https://about.sourcegraph.com/docs https://about.sourcegraph.com/docs [2] https://github.com/sourcegraph/deploy-sourcegraph https://github.com/sourcegraph/deploy-sourcegraph [3] https://about.sourcegraph.com/pricing/ https://about.sourcegraph.com/pricing/ [4] https://github.com/sourcegraph/sourcegraph/blob/master/cmd/server/dockerfile.go https://github.com/sourcegraph/sourcegraph/blob/master/cmd/s... [5] https://about.sourcegraph.com/docs/code-intelligence/install https://about.sourcegraph.com/docs/code-intelligence/install

AsyncAwait 8y ago

Just wanted to say thanks for making code intelligence part of the core product, Sourcegraph has been wonderful!