![]() USER_GID: 1000: The GID (Unix group ID) of the user that runs Gitea within the container.Match this to the UID of the owner of the /data volume if using host volumes (this is not necessary with named volumes). USER_UID: 1000: The UID (Unix user ID) of the user that runs Gitea within the container.USER: git: The username of the user that runs Gitea within the container.Configure the user inside Gitea using environment variables If the database was started with the docker-compose setup asĭocumented above, please note that db must be used as the database hostname. Notice: if using a non-3000 port on http, change app.ini to matchĪfter starting the Docker setup via docker-compose, Gitea should be available using aįavorite browser to finalize the installation. To shut down the setup, execute docker-compose down. Logs can be viewed with docker-compose logs. ![]() Using docker-compose ps will show if Gitea To start this setup based on docker-compose, execute docker-compose up -d, MySQL or PostgreSQL containers will need to be created separately. Named volumes Docker will deal with that automatically. You don’t need to worry about permissions with ![]() This change will automaticallyĬreate the required volume. Within the docker-compose.yml configuration. To use named volumes instead of host volumes, define and use the named volume If you’d like to run the latest commit from a release branch you can use the :1.x-dev tag, where x is the minor version of Gitea. If you don’t give the volume correct permissions, the container may not start.įor a stable release you can use :latest, :1 or specify a certain release like :1.16.9, but if you’d like to use the latest development version of Gitea then you could use the :dev tag. Note that the volume should be owned by the user/group with the UID/GID specified in the config file. Since there is no database available, one can be initialized using SQLite3.Ĭreate a directory like gitea and paste the following content into a file named docker-compose.yml. The most simple setup just creates a volume and a network and starts the gitea/gitea:latest Docker Shell with AuthorizedKeysCommand.Understanding SSH access to Gitea (without passthrough). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |