How to maintain sqlite on the server

I don't think it's a very recommended method because it can slow down the processing speed of the file, such as SMB, or corrupt the file if there is a bug in the network file system and input from multiple locations in the same database at the same time.

See alsoSQLite Documentation Approduce Uses For SQLite Page

If there are many client programs sending SQL to the same database over a network, then use a client/server database engine instead of SQLite. SQLite will work over a network filesystem, but because of the latency associated with most network filesystems, performance will not be great. Also, file locking logic is buggy in many network filesystem implementations (on both Unix and Windows). If file locking does not work correctly, two more clients right try to modify the same part of the same database at the same time, resulting in correction. Because this problem results from bugs in the underlying files implementation, there is not a SQLite can do to present.

A good rule of thumb is to use SQLite sites where the same database will be accessed directly (without an interviewing application server) and simulatively from many computers over a network.

The only problem with downloading, maintaining and uploading locally is that it is difficult to handle any input on the server during maintenance.

I think it would be better to log in to the server with SSH and use the SQLite command line tool for maintenance, but I also think that the simplicity that SQLite benefits is lost.Using SQLite means it's not a very large system, so I think it's okay to do it by "downloading, maintaining and uploading locally."