Better build documentation #68

New Issue

GiteaMirror · 2025-11-02T03:07:24-06:00

GiteaMirror commented

2025-11-02 03:07:24 -06:00

Originally created by @ogarcia on GitHub (Nov 19, 2016).

Add in README or in wiki a better documentation of build using tagged source from github. Something like this.

git clone https://github.com/go-gitea/gitea.git
cd gitea
git checkout latest_tag
etc...

Originally created by @ogarcia on GitHub (Nov 19, 2016). Add in README or in wiki a better documentation of build using tagged source from github. Something like this. ``` git clone https://github.com/go-gitea/gitea.git cd gitea git checkout latest_tag etc... ```

GiteaMirror added the type/docs label 2025-11-02 03:07:24 -06:00

GiteaMirror closed this issue

2025-11-02 03:07:24 -06:00

GiteaMirror commented

2025-11-02 03:07:25 -06:00

@lunny commented on GitHub (Nov 21, 2016):

In fact, go get code.gitea.io/gitea just OK for source installation. You can find this on README.md Installation section.

@lunny commented on GitHub (Nov 21, 2016): In fact, `go get code.gitea.io/gitea` just OK for source installation. You can find this on `README.md` Installation section.

GiteaMirror commented

2025-11-02 03:07:25 -06:00

@ogarcia commented on GitHub (Nov 21, 2016):

Yes, but is for master not for a tagged version 😞

@ogarcia commented on GitHub (Nov 21, 2016): Yes, but is for master not for a tagged version :disappointed:

GiteaMirror commented

2025-11-02 03:07:25 -06:00

@lunny commented on GitHub (Nov 21, 2016):

OK.

@lunny commented on GitHub (Nov 21, 2016): OK.

GiteaMirror commented

2025-11-02 03:07:25 -06:00

@bkcsoft commented on GitHub (Nov 22, 2016):

@ogarcia tagged version should be downloaded as binaries IMO, otherwise you might as well run master.
In other cases you can follow the instructions from development (but add the git checkout $tag yourself :)

@bkcsoft commented on GitHub (Nov 22, 2016): @ogarcia tagged version should be downloaded as binaries IMO, otherwise you might as well run `master`. In other cases you can follow the instructions from `development` (but add the `git checkout $tag` yourself :)

GiteaMirror commented

2025-11-02 03:07:25 -06:00

@ogarcia commented on GitHub (Nov 23, 2016):

@bkcsoft Yes. But, Where is development docs? I think that may be a link to docs into README.md.

And now https://docs.gitea.io/ == Blank page 😞

In Arch Linux and Gentoo prefer make builds from tagged sources than use binaries 😉

@ogarcia commented on GitHub (Nov 23, 2016): @bkcsoft Yes. But, Where is `development` docs? I think that may be a link to docs into README.md. And now `https://docs.gitea.io/ == Blank page` :disappointed: In Arch Linux and Gentoo prefer make builds from tagged sources than use binaries :wink:

GiteaMirror commented

2025-11-02 03:07:25 -06:00

@bkcsoft commented on GitHub (Nov 28, 2016):

In Arch Linux and Gentoo prefer make builds from tagged sources than use binaries

And those who create the PKGBUILD/ebuild-files already knows how to do that 😉 (I'm an Arch-user myself)

@bkcsoft commented on GitHub (Nov 28, 2016): > In Arch Linux and Gentoo prefer make builds from tagged sources than use binaries And those who create the `PKGBUILD`/`ebuild`-files already knows how to do that 😉 (I'm an Arch-user myself)

GiteaMirror commented

2025-11-02 03:07:26 -06:00

@tboerger commented on GitHub (Nov 28, 2016):

A proper documentation page is planned, we need to copy or create a Hugo theme, and than we need to migrate the Gogs docs.

@tboerger commented on GitHub (Nov 28, 2016): A proper documentation page is planned, we need to copy or create a Hugo theme, and than we need to migrate the Gogs docs.

GiteaMirror commented

2025-11-02 03:07:26 -06:00

@bkcsoft commented on GitHub (Nov 29, 2016):

@tboerger "migrate"... under which license are the docs for Gogs? worst-case we have to re-write the docs...

@bkcsoft commented on GitHub (Nov 29, 2016): @tboerger "migrate"... under which license are the docs for Gogs? worst-case we have to re-write the docs...

GiteaMirror commented

2025-11-02 03:07:26 -06:00

@tboerger commented on GitHub (Nov 29, 2016):

I have taken the same license as the Gogs docs to avoid that. First I wanted to do it with a creative commons license, but now it's also apache 2.0.

@tboerger commented on GitHub (Nov 29, 2016): I have taken the same license as the Gogs docs to avoid that. First I wanted to do it with a creative commons license, but now it's also apache 2.0.

GiteaMirror commented

2025-11-02 03:07:26 -06:00

@tboerger commented on GitHub (Nov 29, 2016):

cdfe6a8faf

@tboerger commented on GitHub (Nov 29, 2016): https://github.com/go-gitea/docs/commit/cdfe6a8faffd0c6a2e4ecd279a14978afc965147

GiteaMirror commented

2025-11-02 03:07:26 -06:00

@lunny commented on GitHub (Dec 13, 2016):

So, there are enough documents to resolve this issue?

@lunny commented on GitHub (Dec 13, 2016): So, there are enough documents to resolve this issue?

GiteaMirror commented

2025-11-02 03:07:27 -06:00

@tboerger commented on GitHub (Dec 13, 2016):

The biggest document is https://docs.gitea.io/en-us/hacking-on-gitea/ but we will also write https://docs.gitea.io/en-us/installation-from-source/ with more details.

@tboerger commented on GitHub (Dec 13, 2016): The biggest document is https://docs.gitea.io/en-us/hacking-on-gitea/ but we will also write https://docs.gitea.io/en-us/installation-from-source/ with more details.

GiteaMirror commented

2025-11-02 03:07:27 -06:00

@tboerger commented on GitHub (Dec 21, 2016):

Solved via https://github.com/go-gitea/docs/pull/19

@tboerger commented on GitHub (Dec 21, 2016): Solved via https://github.com/go-gitea/docs/pull/19

GiteaMirror referenced this issue

2025-11-02 11:39:26 -06:00

[PR #68] [CLOSED] Add pagination to release-page #15125

GiteaMirror referenced this issue

2025-11-02 11:39:31 -06:00

[PR #73] [MERGED] Add Pagination to Releases-page (and de-duplicate pagination templates) #15129

Sign in to join this conversation.