Wish B4J Wish - deploy remotely an application to a container

Hello,

For now, I have a NAS drive with docker running on it.
To test my applications, I have a docker image with the b4x bridge.
Secondary, I have a production image that runs the final application.
I first test my programs inside the bridge container, when all is ok, I have the production container, where I copy/replace the jar file to the volume.

The problem is that the b4x bridge stops when you stop debugging, or when you reboot the container, also the application will not run automatically.
A solution for test and upload/run/deploy the application from the IDE would be very nice, so only one container can do it all.

For now the workaround with two containers works fine.

Kind regards,
Coldrestart.

B4J-bridge is only use during debugging. For production, the app need to be compiled in Release mode.

(B4J-Bridge also works in release mode and you can find the compiled jar in the tempjars folder. It will be named AsyncInput1 or AsyncInput2.)

When the application is running in release mode, when the system (container here) will do a reboot, wil the bridge application also start the "released" application also again?
When I reboot the container, the bridge has been started again, but the application in release mode is not running.

The tempjars folder, is it created in the same location as the bridge.jar file?
I need to make this also as presistent storage.

Coldrestart said:

wil the bridge application also start the "released" application also again?

Click to expand...

No.

You will not to create a bash script that starts the jar.

Something like this: https://www.b4x.com/android/forum/threads/server-run-a-server-on-a-vps.60378/#content

Though it is more complicated it is is a UI app. It will be easier to use the MacSigner tool and build a complete package.

Ok, thanks!