Docker guidelines text #249

GiteaMirror commented

@tullo commented on GitHub (Jan 19, 2017):

The readme exists in v0.9 https://github.com/go-gitea/gitea/tree/release/v0.9/docker but did not make it to current version for reasons unknown to me.

@tullo commented on GitHub (Jan 19, 2017): The readme exists in v0.9 https://github.com/go-gitea/gitea/tree/release/v0.9/docker but did not make it to current version for reasons unknown to me.

GiteaMirror commented

@tboerger commented on GitHub (Jan 19, 2017):

Where do you get this information? The docker guide should be part of the docs

@tboerger commented on GitHub (Jan 19, 2017): Where do you get this information? The docker guide should be part of the docs

GiteaMirror commented

@tullo commented on GitHub (Jan 19, 2017):

Maybe add a link to the docs in a minimal readme.
I recently moved my stuff from gogs to gitea and could not remember how i started the gogs docker instance and googled "install gogs docker" where the the first hit gets you to https://github.com/gogits/gogs/tree/master/docker and i guess that the OP made the same assumptions as me and expected to find the info at the same location in the githea repo

@tullo commented on GitHub (Jan 19, 2017): Maybe add a link to the [docs](https://docs.gitea.io/en-us/install-with-docker/) in a minimal readme. I recently moved my stuff from gogs to gitea and could not remember how i started the gogs docker instance and googled "install gogs docker" where the the first hit gets you to https://github.com/gogits/gogs/tree/master/docker and i guess that the OP made the same assumptions as me and expected to find the info at the same location in the githea repo

GiteaMirror commented

@tboerger commented on GitHub (Jan 24, 2017):

Than we should add readme files to every directory. IMHO a docs page is always the first source you should look at, and there you can also directly see it.

@tboerger commented on GitHub (Jan 24, 2017): Than we should add readme files to every directory. IMHO a docs page is always the first source you should look at, and there you can also directly see it.

GiteaMirror commented

@jmn commented on GitHub (Jan 24, 2017):

If Docker guidelines has been written, why not link to them in 74ed6dc3ad/options/locale/locale_en-US.ini (L55)

@jmn commented on GitHub (Jan 24, 2017): If Docker guidelines has been written, why not link to them in https://github.com/go-gitea/gitea/blob/74ed6dc3ad830d308a032fe213e9dfe83f954ffc/options/locale/locale_en-US.ini#L55

GiteaMirror commented

@jmn commented on GitHub (Jan 24, 2017):

By the way, This is how https://docs.gitea.io/en-us/install-with-docker/ looks at the moment for me: (tested with Chromium, Chrome Canary on Windows 10)

@jmn commented on GitHub (Jan 24, 2017): By the way, This is how https://docs.gitea.io/en-us/install-with-docker/ looks at the moment for me: (tested with Chromium, Chrome Canary on Windows 10) ![chrome_2017-01-25_00-27-13](https://cloud.githubusercontent.com/assets/35616/22271579/87887650-e295-11e6-9ece-6f27c80723c2.png)

GiteaMirror commented

@tboerger commented on GitHub (Jan 24, 2017):

That's exactly the part I asked for.

@tboerger commented on GitHub (Jan 24, 2017): That's exactly the part I asked for.

GiteaMirror commented

@lunny commented on GitHub (Jan 25, 2017):

It's a UI bug. @jmn could you fire an issue on go-gitea/docs ?

@lunny commented on GitHub (Jan 25, 2017): It's a UI bug. @jmn could you fire an issue on go-gitea/docs ?

GiteaMirror commented

@jmn commented on GitHub (Jan 25, 2017):

OK see go-gitea/docs/issues/85

@jmn commented on GitHub (Jan 25, 2017): OK see go-gitea/docs/issues/85

GiteaMirror commented

@lunny commented on GitHub (Jan 25, 2017):

Thanks.

@lunny commented on GitHub (Jan 25, 2017): Thanks.

GiteaMirror commented

@tboerger commented on GitHub (Jan 25, 2017):

@lunny why should he report a theme issue to the docs?

@tboerger commented on GitHub (Jan 25, 2017): @lunny why should he report a theme issue to the docs?

GiteaMirror commented

@lunny commented on GitHub (Jan 25, 2017):

@tboerger you mean that's hugo's bug?

@lunny commented on GitHub (Jan 25, 2017): @tboerger you mean that's hugo's bug?

GiteaMirror commented

@tboerger commented on GitHub (Jan 25, 2017):

@lunny no, a theme bug. I'm pretty sure this is related to an unproperly pinned bootstrap version. As MetalMatze used the bootstrap 4 beta and they switched the grid system

@tboerger commented on GitHub (Jan 25, 2017): @lunny no, a theme bug. I'm pretty sure this is related to an unproperly pinned bootstrap version. As MetalMatze used the bootstrap 4 beta and they switched the grid system

GiteaMirror commented

@jmn commented on GitHub (Jan 25, 2017):

It's hard to know which repo to report to for the website. The website shares the theme with Gitea the app?

@jmn commented on GitHub (Jan 25, 2017): It's hard to know which repo to report to for the website. The website shares the theme with Gitea the app?

GiteaMirror commented

@tboerger commented on GitHub (Jan 25, 2017):

The repo "theme" is the shared Hugo theme for the website, docs, blog and code redirects.

@tboerger commented on GitHub (Jan 25, 2017): The repo "theme" is the shared Hugo theme for the website, docs, blog and code redirects.

GiteaMirror commented

@lunny commented on GitHub (Jan 25, 2017):

So this issue should be moved to go-gitea/theme?

@lunny commented on GitHub (Jan 25, 2017): So this issue should be moved to go-gitea/theme?

GiteaMirror commented