Added guidance on file to choose to download

[apxltd]

To help clarify which file to download, I added some guidance on what the different files mean.

[apxltd]

@a1012112796 I think I updated the file now :)

[apxltd]

@zeripath I'm just a Windows dummy who couldn't figure out what file to download and had no idea what gogit is. I just wanted to try to make it easier for other dummies to figure out how to install Gitea 😉

Someone should decide for dummies like me if we should start with gogit-windows or windows, and tell us when to try the other. I tried to explain, but still I don't get it. I suppose could edit the documentation to encourage the reader to "flip a coin" and try the other one if it doesn't work... but I figure the smart people like you could say something better 😆

If you can tell me what to write, I can write it - but it might be faster for you to just edit what I wrote to be technically accurate.

[apxltd]

@zeripath ooh as for 32-bit and 64-bit.... there really isn't 32-bit Windows anymore, I mean.. not since Windows Server 2008 (which is out of support). Is the same true on Linux? Would you be OK if we clarify, for the younguns who've never seen a 32-bit operating system, that they probably just want 64-bit... but they can use the 32-bit ones if they have an old OS?

[zeripath]

@zeripath I'm just a Windows dummy who couldn't figure out what file to download and had no idea what gogit is. I just wanted to try to make it easier for other dummies to figure out how to install Gitea wink

Someone should decide for dummies like me if we should start with gogit-windows or windows, and tell us when to try the other. I tried to explain, but still I don't get it. I suppose could edit the documentation to encourage the reader to "flip a coin" and try the other one if it doesn't work... but I figure the smart people like you could say something better laughing

If you can tell me what to write, I can write it - but it might be faster for you to just edit what I wrote to be technically accurate.

I don't use windows and so I can't tell you which to try.

We provide the go-git builds because some windows users find that using the git binary calls makes things too slow - however, these users are unable or unwilling to debug further or provide us with further explanations other than Gitea is slow.

I think the point is to say - try both and see which is quicker for you. Gogit appears quicker for at least some people but despite asking people to tell us whether that is always the case no-one has told us. If it was obvious which was better we'd provide only one build - but we don't have the information - thus there's a reason why both builds are provided.

[apxltd]

@zeripath thanks for the guidance

I tried to articulate why gogit exists, and when to use it. This will also help you gather data.

I researched a bit more about 32-bit, arm5/6, and those seem really rare these days. I couldn't even see where to download 32-bit ubuntu anymore.

"Apple Silicone" is apparently what they call it, and it looks like it's a crapshoot now as to what users have.

[wxiaoguang]

Now there is a markdown linter 😁

• Add markdownlint #20512

So there are some lint errors during CI to be fixed.

https://drone.gitea.io/go-gitea/gitea/58210/1/4

npx markdownlint docs *.md

docs/content/doc/installation/from-binary.en-us.md:27:153 MD009/no-trailing-spaces Trailing spaces [Expected: 0; Actual: 1]

docs/content/doc/installation/from-binary.en-us.md:29 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### Choosing the right file"]

docs/content/doc/installation/from-binary.en-us.md:31:1 MD009/no-trailing-spaces Trailing spaces [Expected: 0; Actual: 1]

docs/content/doc/installation/from-binary.en-us.md:41 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```sh"]

docs/content/doc/installation/from-binary.en-us.md:48 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]

make: *** [Makefile:316: lint-frontend] Error 1

[apxltd]

@wxiaoguang I feel I'm allllmost there, hopefully this fixes the problem of the markdown :)

[wxiaoguang]

The improved content looks good to me.

ps: I am not a native speaker for English, not sure whether the syntax ..., but there are other platforms available (the but) is a common one in English.

[lunny]

make L-G-T-M work