Actually session functions are written at server/middleware, normally we should keep only the middleware functions, and move other logic to pkg/session

Check here $GOPATH/src/github.com/medtune/beta-platform whenever static path is not provided

pkg/Inits is responsible for initialising all necessary packages that are used by the server.

We need two different modes for running inits: Debug and Production. Debug mode should allow skipping some initialisations while Production mode need to panic() whenever something is going wrong at startup.

Better than cookies or memcached. Use Redis.

For example for user model we can have functions that directly handles users authentication /creation etc ... same for all other models

Implementing basic models. Probably using Postgres as database. To confirm.

Before diving into Capsules project, we could create a simple client that will handle inference and look ups on Tensorflow freezed models.
Keep in mind that gRPC is required also TensorflowServing signatures

at pkg/validator we need a certain API for validating data objects all sort of uploaded images/videos/archives etc
Keep in mind extensions aren't enough for validating files. Reading headers is the right way.

Separating application logic from the user interface, in order to accelerate design developpement and isolate business components.

go run main.go --debug to show-up all compiled templates would be awesome

Needed command line formats:

Startup pre check

medtune-beta start

Run server

medtune-beta start --port=8080 --debug=true

Get version

medtune-beta version

Sync models

medtune-beta sync-db

Instead of handling session logic at each route , it would be easier to set a middleware for all private content:
Something like this example works but only if we abort connection.

import (
	"github.com/gin-contrib/sessions"
	"github.com/gin-gonic/gin"
)

func LoggedOnly() gin.HandlerFunc {
	return func(c *gin.Context) {
		s := sessions.Default(c)
		if v := s.Get("logged"); v == nil || !v.(bool) {
			c.AbortWithStatus(404)
			return
		}
	}
}