as suggested by @lafriks and @techknowlogick i move the issue and marked questions about gitea build and distributions for distribution and other developers that need ad-hoc solutions or wants to improve documentation
Firts of all, i introducted: there’s two important topics, gitea are distributed as a binary with build-in asstes and files inside the binary itselft, that’s souns good until that binary becomes too big and undistributable, documentations only arge that “easy”, “quick”, “selft-contained”, but when administrators are in hurry, must come to this forums or try to be lucky in the gitea issues … but that’s the problem, are in hurry, and its supposte that documentation are here!
Second, building from sources to be possible modifications for ad-hoc solutions are difficult, due “administrators” can see “Feature Comparison Data Sheet”(https://docs.gitea.io/en-us/comparison/) but cannot implement this “fast” and then the management (Managers) decides for it’s administrators and implements a proprietary solution, i mean, by example said: “CSV support” but what that means? CSV support for what? and how?
Q 1: @techknowlogick said “If you build from source without bindata tag, then files being in the same path as gitrepo” but obviously they not read carefully my question when i said: " so we do not will include all the gitea sources of course!" so i ask AGIAN: what files only to run without use bindata build!
Q 2: @techknowlogick said “Make sure to keep built binary (for dev) in root of git repo so it can use assets if not bundled into binary.” that are not good and are not possible, i partiuculary see that cmake does, the build process are apart of original sources, this keep clean the work when i do something bad! of course we have the git management command line, but as i said, we are always in hurry and administrators or users dont wants to spend too much time deploying gitea… but wants to deploy very customized of course… so i ask : can explain more the changes in build process to tray to document that?, by example: there’s a new tag build named “sqlite_unlock_notify” but to find information about, i must to go to commits!!, that’s its too much spend of time for administrators that wants to deploy an ad-hoc solution and search for more!
Q 3: i want to know how exactly we can all of us as administrators or users, deploy a gitea as cgi application¡? i mean: obviously must be using a socket path but as deamon? a cgi as daemon? fi yes, could be possible run as normal cgi with no-daemon mode?
