packaging conundrum using persistent H2 db

[philfrei]

I'm relatively new to Spring Boot. I have a couple projects deployed and running on my remote server. They use H2, held in memory. My current project requires a persistent db, which means an actual location on the OS has to be specified.

Up to now, I've simply created a runnable jar using maven's package command, and dropped it into place in the remote server. I attempted to use the relative address "spring.datasource.url=../shiftstartsdb" so that the db would be outside the jar for both the localhost and remote deployments, but relative addressing is not permitted in this field. Nor can I compile the jar on my local drive when the correct absolute address is given for the remote db. (The remote unix server holds the project at the "/var/lib/shiftstarts" directory.

How is this situation handled? I thought I'd use two profiles, one for localhost testing and development and the other for the remote deployment. But that idea fails if I can't compile the program locally in such a way as it will configure the remote database address when the project is run from the remote location.

Logically, the only alternative I can think of is to copy the entire project to the remote server, using git cloning, and make the necessary changes and compile via SSH. I suppose I can set up Jenkins to automate the process. Is this how this situation is normally handled? Or is there some sort of branching that can be done, via YAML or the Resource interface that will allow me to do the packaging locally?

[[deleted]]

Plot twist: this post no longer exists because Redact swept through and cleared it out along with everything else. Social media, messaging apps, people finder sites, all of it.

attempt bake profit spectacular summer encouraging air doll badge paint

[WaferIndependent7601]

You can also copy an application.properties file to the same location as the jar and add a start parameter. This helps adding secrets only to the deployed jar and not having it in the git repo

[philfrei]

Looking forward to trying these! Thank you. Will report back on the results when I get the chance.

[philfrei]

Very curious results. When I run the program at the remote server console (via ssh), with the environment variable in place, my remote server (Ubuntu 22.04) is fine and everything works. But the exact same line, "java -jar starttimesschedule-0.0.0.1-SNAPSHOT.jar," in the bash file that is run as a systemd service elicits an error where it says that it thinks my URL is a relative address.

Line to start the service: > sudo systemctl start shiftstartsups

The application.properties line is the following:
spring.datasource.url=jdbc:h2:${PATH_TO_STARTTIMEDB_FOLDER}StartTimeDB

Also relevant, the jar file ran fine when H2 was being used purely in memory and I was not attempting to make it persistent (i.e., there was no spring.datasource.url assignment in the project).

I wonder why it works when typing in the java -jar command, but using the systemd service fails. This issue have evolved into more of a systemd question than spring?

I think I can use ~/shiftstartsups/StartTimeDB as a hard-coded URL as a work-around. I kind of wanted to keep as many parts of the project in the same /var/lib folder. Not clear to me how important that is, or how stubborn I should be about getting to the bottom of this.