goapp | An opinionated guideline to structure & develop a Go web application/service | REST library

I have a very simple Go app that I'm trying to Dockerize.

Im doing a hashed password generator, i have an endpoint at the server that generates a goroutine to create the hashed password, and then send it as a response when the goroutine ends.

this is the function that is called to generate the hashed password

I want to set a safety zone by device. My web view is set to SafeArea above, SuperView below. After the iPhone X series, the value of Y is 44 because of the notch area. But for the iPhone 6 and iPhone 8, 44 is too wide. How do I adjust it?

I am using go module, the file structure is like this:

We are running a Golang application that internally runs an autoupdate module to recieve over the air updates. At the time of a new update, the autoupdate module downloads the new version from s3 and invokes an autoupdate bash script present in the same working directory as the executable. The steps performed by the autoupdate bash script are explained in terms of process management handled with and without systemd.

Execution without Systemd

1. Kills the currently running golang app via PID
2. Runs the newly downloaded golang binary.
3. The new version exposes an health check API which is invoked by script to makesure this version is healthy.
4. If not healthy, rollback is performed. The new version is stopped and older version is started.

In golang, the script execution code is written such that when autoupdate script is invoked, it is disowned from the lifecycle of the golang application. i.e bash script (child process) continues execution even after the parent(golang app) is killed. It works fine when running from the GoLand IDE.

Issue : Execution via Systemd

We needed a cleaner system to handle the start ,stop, restart-on failure functionalities. So we decided to run the app as a systemd service.The steps are the same as above but performed using systemctl

1. Kills the currently running golang app : "systemctl stop goapp.service"
2. Updates the systemd service with the new executable path : "systemctl daemon-reload"
3. Restarts the systemd service : "systemctl restart goapp.service"
4. If not healthy, rollback is performed. The new version is stopped, systemd service file is updated with older version and older version is started.

On executing the application via systemd, the script exits as soon as the systemctl service is stopped using command "sudo systemctl stop goapp.service" during step 1 mentioned above. This means that the lifecycle of the script executed by the golang app is clearly coupled to the lifecycle of the systemd service. How can I detach it from the of scope of systemd service?

Systemd service file

I have a simple API written in GO using Mux.

When running locally it works, however I am trying to containerize this app.

My main.go looks like this

I've been updating my entire go gae standard project to use go 1.11's modules.

Main directory structure

I'm tying to write tests for my google cloud app. I read the documents and it seems the only way to run the test locally is the running the command goapp test in the test package directory. But when I run the command I get the error go: GOPATH entry is relative; must be absolute path: "".

I'm pretty sure my GOPATH is set absolutely. Here are the results when I run the command go env | grep GOPATH:

GOPATH=":/home/mohammad/go:/home/mohammad/go/src/gitlab.com/gc-auth"

Also getting the same output when I run echo $GOPATH.

Any help is appreciated.

PS: I have ubuntu 18.04 and my go version is 1.10.4

results of gcloud version:

Google Cloud SDK 228.0.0 app-engine-go app-engine-python 1.9.80 bq 2.0.39 cloud-datastore-emulator 2.0.2 core 2018.12.07 gsutil 4.34

I use Docker to add my project to it, now I want to run some test on it and I got errors that the test failed

Any idea what I miss here?