Developement Server

I have successfully implemented a development server, running on https://beta.dev.languagelab.be, and updated on every commit to dev. As we cannot yet use https://dev.languagelab.be (I don't know where we are on that with SGSI?), the development back-end is available at https://beta.dev.languagelab.be/tmp-api. But the certificate we use is only valid for https://languagelab.be, https://api.languagelab.be and https://dev.languagelab.be, so the requests to the API fail due to bad certificate. So for now, I've connected the development front-end to the production back-end. So as soon as we will introduce changes in the back-end, it will no longer works.

In my opinion it would be nice to ask the SGSI to:

1. Fix the DNS for https://dev.languagelab.be and https://api.languagelab.be (in priority)
2. Get a wildcard certificate that include *.dev.languagelab.be and *.api.languagelab.be (as it's the case for the DNS). And if they don't allow us to have wildcard certificates, at least for https://api.dev.languagelab.be.

changed milestone to %0.2: Essential functions ready & corrective feedback

added Bug Open for discussion labels

assigned to @sbibauw

@DavePikopPokam @dvanrossum for info

mentioned in issue #166

marked this issue as related to #166

• I submitted a ticket to ServiceDesk yesterday to solve 1. It's in progress.
• Is that enough or do you want me to also request the certificate for https://api.dev.languagelab.be? (or wildcard .dev/.api if possible)

closed