wip! feat(symphony-ws): Add Dockerfile

[zapling]

Attempt to add a Dockerfile for the backend. This one compiles and starts the wildfly instance with the compiled war file. Currently it fails to connect to a database (because there is none)

[zapling]

Not sure if symphony-ws requires a specific name here.

[zapling]

The readme mentions the standalone-full.xml but unsure what the difference is

[ann-hav]

Just discovered this fork! Kudos 👏 Did you mean to bring this to our attention on the upstream? Or is this PR for internal review at @fabled-se ?
I'd love to take a look at this, maybe next week.

/ Ann på HaV

[zapling]

We where looking into running this app inside Kubernetes, we are working a bit with Ocean Data and they wanted to know how hard it would be to host it.

Is there an official interest in providing a dockerfile for the project, our interest is otherwise pretty low in trying to upstream, since the use-case of packaging and running this inside kubernetes seems pretty niche?

[ann-hav]

No, this honestly isn't prioritised at our end.
Like it says in our issue description (havochvatten#49), primarily a workable docker image may be desirable for us in that it would allow us to run the suite of API tests in the Github CI pipeline. This would be "nice to have" but it's not exactly crucial.
That said, all contributions are encouraged, and of course we'd be happy to incorporate a working solution!

Regarding your pursuit of a setup with Kubernetes, my guess is that heap memory could become an issue for you since Symphony can be quite RAM intensive when working with large rasters. But I don't have a lot of experience with Kubernetes.

I feel I should confess however, being the maintainer of this project, it occurs to me that regrettably part of the enclosed documentation is out of date. In particular database/DataImportREADME.md doesn't accurately describe the current procedure for providing metadata at this point. Just wanted to mention this, to perhaps anticipate any problems in achieving a working setup if you'll be moving forward with this. I'll look into getting this fixed appropriately, in the meantime I'll go ahead and remove any misleading information on the upstream.