Problems self-hosting on Debian (from Issue #3062)

[mngshm]

@Jerroder I am answering all your queries here for now. For those who might feel contextless, please check issue #3062.

Hey, extremely sorry for not making the documentation verbose. That documentation is quite old now and I made a updated version recently. But I think it still does lack some verbosity, I'll make sure to add more instructions on my next working day.

Now in Start museum, I need to set the variable ENTE_DB_USER to postgres but if I use air for live reloads, the user is ente_user?

Extremely sorry for the above. It looks like this was mistake. Just now I ran Air (for the first time) and you're right it has to be ENTE_DB_USER=postgres both the times. But, if you've already exported it as postgres then you don't have to do the variable setting before running air (again, sorry I'll improve the doc).

When I ran this, it downloaded a bunch of stuff and then exited without any error. Is this expected

The reason we mentioned the command go run cmd/museum/main.go to be run from ente/server dir is because the configurations/local.yaml and the whole environment is in the root directory of museum (server). Maybe try cleaning your go cache by running go clean -modcache and re-running the command from the servers root dir which is ente/server. please let me know if its not fixed.

Also, that isn't the expected behavior, it should be something like the below screenshot (from my own server).

Please note I'm running museum with Air

Do I need to fill museum.yaml with DB user and password?

Yes.

And museum.yaml should be created "in the current directory" but where is that? ente/? ente/server/?

It should be in the ente/server directory, but this is only comes in use if you want to override stuff which is there in ente/server/configurations/local.yaml.

If it works eventually, how do I stop, start and reload it?

What exactly ? Museum or Air ?

For both Museum and Air, you can do a simple ctrl+c and make sure to kill the port :8080 (or whatever you have custom configured), so that the next time you can start museum without any errors.

Regarding reloads in Air, I'm not sure if Air has any reload kind of feature.

You can do a simple lsof -i :8080 and kill the PID.