Description on Docker Hub is boring #1450

New Issue

GiteaMirror · 2025-11-02T04:01:17-06:00

GiteaMirror commented

2025-11-02 04:01:17 -06:00

Originally created by @kolaente on GitHub (Jan 14, 2018).

IMHO, the description on https://hub.docker.com/r/gitea/gitea/ is really boring. It should have at least a link to the website and a short description about what Gitea is. Also a link to docs, maybe even an example docker compose file to quickly set it up (I have one which I'd be happy to share) would be great.

What do you think?

Originally created by @kolaente on GitHub (Jan 14, 2018). IMHO, the description on https://hub.docker.com/r/gitea/gitea/ is really boring. It should have at least a link to the website and a short description about what Gitea is. Also a link to docs, maybe even an example docker compose file to quickly set it up (I have one which I'd be happy to share) would be great. What do you think?

GiteaMirror added the type/proposal label 2025-11-02 04:01:17 -06:00

GiteaMirror closed this issue

2025-11-02 04:01:17 -06:00

GiteaMirror commented

2025-11-02 04:01:17 -06:00

@lunny commented on GitHub (Jan 14, 2018):

@kolaente I think you are right. Please give the text what you think it should be. And any others could also give more idea. After this issue end, we can change that description.

@lunny commented on GitHub (Jan 14, 2018): @kolaente I think you are right. Please give the text what you think it should be. And any others could also give more idea. After this issue end, we can change that description.

GiteaMirror commented

2025-11-02 04:01:18 -06:00

@thehowl commented on GitHub (Jan 14, 2018):

quickly wrote a draft: https://gist.github.com/thehowl/cd950ae33a8519439ac58a644037bb1f

@thehowl commented on GitHub (Jan 14, 2018): quickly wrote a draft: https://gist.github.com/thehowl/cd950ae33a8519439ac58a644037bb1f

GiteaMirror commented

2025-11-02 04:01:18 -06:00

@kolaente commented on GitHub (Jan 14, 2018):

Dockerfile (with description):

Use this dockerfile to get up and running quickly. You should change mysql user- and root password. When installing, you can reference the database container as host db.

This configuration will publicly expose ports 3000 and 22.

version: '2'
services:
  web:
    image: gitea/gitea:1.3.2
    volumes:
      - ./data:/data
    ports:
      - "3000:3000"
      - "22:22"
    depends_on:
      - db
    restart: always
  db:
    image: mariadb:10
    restart: always
    environment:
      - MYSQL_ROOT_PASSWORD=changeme
      - MYSQL_DATABASE=gitea
      - MYSQL_USER=gitea
      - MYSQL_PASSWORD=changeme
    volumes:
      - ./db/:/var/lib/mysql

@Off-Topic: is it currently possible to configure gitea with environment variables?

@kolaente commented on GitHub (Jan 14, 2018): Dockerfile (with description): Use this dockerfile to get up and running quickly. You should change mysql user- and root password. When installing, you can reference the database container as host `db`. This configuration will publicly expose ports `3000` and `22`. ```Dockerfile version: '2' services: web: image: gitea/gitea:1.3.2 volumes: - ./data:/data ports: - "3000:3000" - "22:22" depends_on: - db restart: always db: image: mariadb:10 restart: always environment: - MYSQL_ROOT_PASSWORD=changeme - MYSQL_DATABASE=gitea - MYSQL_USER=gitea - MYSQL_PASSWORD=changeme volumes: - ./db/:/var/lib/mysql ``` @Off-Topic: is it currently possible to configure gitea with environment variables?

GiteaMirror commented

2025-11-02 04:01:18 -06:00

@sapk commented on GitHub (Jan 15, 2018):

@kolaente yes done in #2201 and #2791

@sapk commented on GitHub (Jan 15, 2018): @kolaente yes done in #2201 and #2791

GiteaMirror commented

2025-11-02 04:01:18 -06:00

@xy2z commented on GitHub (Feb 20, 2018):

@kolaente Shouldn't the image be gitea/gitea:latest?

@xy2z commented on GitHub (Feb 20, 2018): @kolaente Shouldn't the image be `gitea/gitea:latest`?

GiteaMirror commented

2025-11-02 04:01:19 -06:00

@sapk commented on GitHub (Feb 20, 2018):

If I am not mistaken, latest is on master that is not stable. We could provide a "stable" tag or maybe switch latest to last "stable" version. It reflect the branch on git master -> latest is unstable and branches for each version that receive backport when needed. Gitea at the start of the fork, receive a lot of change and was to be consider a work in progress as we break things maybe now we could start to provide stable instance.

@sapk commented on GitHub (Feb 20, 2018): If I am not mistaken, latest is on master that is not stable. We could provide a "stable" tag or maybe switch latest to last "stable" version. It reflect the branch on git master -> latest is unstable and branches for each version that receive backport when needed. Gitea at the start of the fork, receive a lot of change and was to be consider a work in progress as we break things maybe now we could start to provide stable instance.

GiteaMirror commented

2025-11-02 04:01:19 -06:00

@kolaente commented on GitHub (Feb 20, 2018):

I think master is generally stable, but not guaranteed. So I wont nessecary use master (aka latest) in production.

@kolaente commented on GitHub (Feb 20, 2018): I think master is generally stable, but not guaranteed. So I wont nessecary use `master` (aka `latest`) in production.

GiteaMirror commented

2025-11-02 04:01:19 -06:00

@kolaente commented on GitHub (Mar 3, 2018):

So, can we update it then to the description provided by @thehowl ?
@maintainers

@kolaente commented on GitHub (Mar 3, 2018): So, can we update it then to the description provided by @thehowl ? @maintainers

GiteaMirror commented

2025-11-02 04:01:19 -06:00

@lunny commented on GitHub (Mar 3, 2018):

@kolaente Since nobody have further idea, I think yes.

@lunny commented on GitHub (Mar 3, 2018): @kolaente Since nobody have further idea, I think yes.

GiteaMirror commented

2025-11-02 04:01:19 -06:00