Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[help] Gitea cannot run in the Windows development environment #9389

Closed
scotox opened this issue Dec 17, 2019 · 3 comments
Closed

[help] Gitea cannot run in the Windows development environment #9389

scotox opened this issue Dec 17, 2019 · 3 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@scotox
Copy link

scotox commented Dec 17, 2019

  • Gitea version (or commit ref): source branch v1.10.1
  • Operating system: Windows10 x64

Description

  1. goland 2019.2
    • Enable Go Modules (vgo) integration
    • Proxy: goproxy.io
    • GOROOT and GOPATH is ok.
  2. go version go1.13 windows/amd64
  3. goland Run/Debug Configurations to Go Build
    • Run kind: File
    • Files: xxx\code.gitea.io\gitea\main.go
    • other is default
  4. run Debug to panic.

panic: fail to set message file(en-US): open conf/locale/locale_en-US.ini: The system cannot find the path specified.

Screenshots

image

@jolheiser
Copy link
Member

https://docs.gitea.io/en-us/install-from-source/#build
https://docs.gitea.io/en-us/make/

Simply running main.go will not work, doubly so because GoLand runs the built binaries in temp build locations.
It may be possible for GoLand to run it correctly if given the correct tags so that assets are bundled, but it's probably a better strategy to use the documented way for the time being.

@zeripath
Copy link
Contributor

I suppose we could wrap our CSS and js generation steps in go:generate then you don't need the make step...

@lunny lunny added type/question Issue needs no code to be fixed, only a description on how to fix it yourself. issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail labels Dec 18, 2019
@scotox
Copy link
Author

scotox commented Dec 18, 2019

TKS All the guys

The problem was solved ...... the goland Run/Debug Configurations has three fields ("Directory", "Output directory", "Working directory"), I left out the "Output directory" item .... set this item to project root path then it's all right ..... not on the make of command line .... not on the npm build ......
go straight to code breakpoint mode.
Now i can have a happy break point again.....

@scotox scotox closed this as completed Dec 18, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

4 participants