Make backend more compatible with windows

FUB-HCC / IKON-projektor

Frontend component for https://github.com/FUB-HCC/IKON-backend

https://fub-hcc.github.io/IKON/

GNU Affero General Public License v3.0

5 stars 2 forks source link

Make backend more compatible with windows #192

Closed mx-e closed 4 years ago

mx-e commented 4 years ago

Because the app is supposed to be run on Windows at the museum, it is important that the backend is fully able to be run on Windows and that the installation process is fairly painless. At the moment the execution part of this is elegantly ensured through Containerisation.

However, the build script is not optimised for any shell on Windows (for example git bash) and needs several modifications to run. For example:

an env variable to prevent a problem with some flags in the key-gen process
changes to file/folder permissions (those apparently work differently on Windows) (for used hot fixes see below)
[ ] adapt and test the shell script to make the install workflow as close to the one expected by the user from the install guide
[ ] alternatively make an install guide specifically for Windows

Photo_1

wittenator commented 4 years ago

The plan is to not use a local deployment of the application on the touch pc in the museum since it poses a major maintenance burden.

mx-e commented 4 years ago

there needs to be a reasonably painless way to test the touch version of the front-end with an actual touch screen.

Is there any infrastructure for a production deployment of the backend, with a public (or for that matter password or somehow-else protected) way to access it ? How do i access it ? (Via ssh or physically ?)

ckinkeldey commented 4 years ago

It was our initial plan to have a version running at all times and make it accessible, e.g., via ssh or so. But we never got there. @wittenator wouldn't it be a good way of testing the deployment?

wittenator commented 4 years ago

Yeah, I can deploy a version on the free credits of GCP. Since there are a bootload of other features atm, I need a prioritisation from your side though. The deployment procedure would also be different to the one in the museum if I don't do the image pushing in time.

wittenator commented 4 years ago

I would just secure it via a basic auth in that case

ckinkeldey commented 4 years ago

Yes, it is high priority because of the testing phase. https://github.com/FUB-HCC/IKON-backend/issues/36 Thanks

mx-e commented 4 years ago

ill close this and make an issue for hosting over at backend