Question 1

How do I use Gebug with Visual Studio Code for debugging?

Accepted Answer

Gebug sets up Delve on a default port (40000); in VSCode, create a launch config to attach to localhost:40000. The demo GIF shows this integration, and you can adjust the port in config.yaml if needed.

Question 2

Is Gebug or manual Docker setup better for Go debugging?

Accepted Answer

Gebug saves time by auto-generating configs, ideal for standard Go apps in Docker. For highly customized builds or advanced Docker features, manual setup might offer more control and flexibility.

Question 3

Can Gebug work with Kubernetes instead of Docker Compose?

Accepted Answer

No, Gebug is built around Docker and Docker Compose; for Kubernetes, you'd need to manually adapt the generated files or use other tools specific to k8s debugging environments.

Question 4

How to add custom build commands in Gebug?

Accepted Answer

Edit the config.yaml file in the .gebug directory, modify the 'build_command' field, and use 'gebug start --skip-generate' to apply changes. The Web UI also allows edits through a browser interface.

Question 5

Does Gebug support debugging multiple services at once?

Accepted Answer

It uses docker-compose, so you can configure multiple services in the generated files, but Gebug's primary focus is on a single Go application; multi-service setups may require manual docker-compose extensions.

Question 6

What are the performance implications of using Gebug's hot-reload?

Accepted Answer

Hot-reload rebuilds on every change, which is fine for small projects, but for large codebases, build times might slow down the iteration cycle unless you optimize the build_command in config.yaml.

Gebug

What is Gebug?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions