Quick question,wonder is it possible to temporarily disable the database, about borg_calendar HOT 6 CLOSED

kinda like gui read only state.and anyone can try and touch it but it will not have the edited change.

from borg_calendar.

The database is a local file. the default is an H2 database. I currently use Sqlite - #154. the port is not database related.

The port that is opened is just used to prevent 2 Borgs from being opened. When you start Borg, it checks this port to see if another Borg is already running and if so, it will send a message to the running Borg to open itself.

I'm not exactly sure what you are trying to do.

from borg_calendar.

the aim is to have a readonly database and the gui and no sockets exposed.
I see h2 db has a read only mode.maybe that's possible to be utilized.

for the socket exposed maybe we can instead,use a borg.lock file(when uses read only mode)?
just like those common documemnt editing software,eg libre office.

from borg_calendar.

the main reason for no port exposed is for having absolute certainty that when you use borg in a public wi-fi port scanning attack just doesnt work.

from borg_calendar.

There is no database port exposed. You can also disable Borg from opening its port in the options. However, this port should not be exposed to wifi - it does not need to be opened through your firewall. There is also no security risk exposed by this port. The only data sent over the port is the string "open" to tell a running Borg to open itself. No data can be read from the port.

Borg is not written to expect the DB to be open read only have all writes fail. It will error.

I still dont understand the use case. Are you trying to give another person read-only access?
The database is just a local file to Borg. There is no running database server that can be accessed from outside Borg. The database is opened by Borg in embedded mode. It is just a file.

from borg_calendar.

yeah you are right

I see.hmmm.

Yeah,in the case of maybe showcase or something.
1 work around is to just point db to another place and then restart borg.

I think this issue is kinda resolved so will close the issue

from borg_calendar.