gogs | Gogs is a painless self-hosted Git service | Continuous Deployment library

You should connect both containers to the same docker network and then proxy to http://gogs:3000 instead. You also shouldn't need to expose port 3000 on your localhost unless you want http://app.test.local:3000 to work. I think ideally you should remove that, so http://app.test.local should proxy to your gogs server, and http://app.test.local:3000 should error out.

gogs is exposed on port 3000 inside its container, which is then further exposed on port 3000 on your host machine. The nginx container does not have access to port 3000 on your host, so when it tries to proxy to http://localhost:3000 it is proxying to port 3000 inside the nginx container (which is hosting nothing).

After you have joined the containers to the same network, you should be able to reference the gogs container from the nginx container by its hostname (which you've set to gogs). Now nginx will proxy through the docker network. So you should be able to perform the proxy without needing to expose 3000 on your local machine.

On a Raspberry Pi, RAM is limited and you can't easily add more. In situations where you need more RAM (which is the case for this GOGS failure), the solution is to use or increase the size of a swap file.

In my case, a swap file was already configured for 100M, but insufficient. Increase it (e.g. 1G):

1. Disable temporarily swap file: sudo dphys-swapfile swapoff
2. Edit file /etc/dphys-swapfile and modify CONF_SWAPSIZE. Example: CONF_SWAPSIZE=1024
3. Setup system with this size: sudo dphys-swapfile setup
4. Re-enable swap file: sudo dphys-swapfile swapon

This solves the issue I have, where the Git server fails on the RPi because it lacks RAM.

Download a zip archive of a remote Git repository (be it a gogs one, or any other remote hosting service), means downloading a snapshot view of the default HEAD.

There is no history.
The history you have created by initializing a local repository in it, and creating a branch, has no common base with the one from the original remote repository.

If you want to push back your local branch, you need first to:

• clone the repository
• add your local repo as a remote to the official cloned one, and fetch
• create a new branch
• cherry-pick from the fetched branch to the new branch (and you can cherry-pick in one command a range of commits)
• push back the new branch (which will work, since you are pushing from an actual clone)

That is:

You can read the file with pandas.read_csv() with error_bad_lines=False:

You can inspect the container to find where are the files on the host that are associated with the container

1. Find the container name docker ps

2. Use docker inspect to find where are the files related to the container.

Depending on how the volumes and the container was created, you can see the folder associated with the base image as

The gist of this error is that the version of binary used to generate the code isn't compatible with the current version of code. A quick and easy solution would be to try updating the protoc-gen-go compiler and the gRPC library to the latest version.

go get -u github.com/golang/protobuf/protoc-gen-go

then regen the proto

heres a link to a reddit thread that discusses the issue

I fix it by installing Drone on a dedicated instance. It seems like an obscure network problem.

Drone doc

Please note we strongly recommend installing Drone on a dedicated instance. We do not recommend installing Drone and Gitea on the same instance using docker-compose due to network complications.

Alright, between Front and Backend i must have overlooked that my uWSGIservice for my App is mapping my static folder / STATIC_URL. I forgot about this.

On the other hand STATIC_ROOT is maybe semantically misleading - unlike MEDIA_ROOT - STATIC_ROOT is only collecting static files in a folder, when collectstatic is executed. I mixed that up. I guess something like STATIC_COLLECT would be more obvious, to differentiate.

However now static and media files are working in my production.

blackbird_app.ini (uWSGI)

Selecting from user will return your username. In order to select from a table of that name, you need to prefix it with the schema name, and in this case it is public. So you will need to execute: