search

me-box / databox

Databox container manager and dashboard server
MIT License
94 stars 25 forks source link

https://export.amar.io/ expired certificate #161

Closed tsh-box closed 7 years ago

tsh-box commented 7 years ago

Hello, Export destination url https://export.amar.io/ cannot access because of the expired certificate

err2

yousefamar commented 7 years ago

Thanks for letting me know, I've renewed it now.

haddadi commented 7 years ago

Can we make a note to move this to a databox sever eventually?

thanks

mor1 commented 7 years ago

(sooner rather than later- by thursday?)

yousefamar commented 7 years ago

Should be quick to deploy on any server. Pure Node, no native deps: https://github.com/me-box-archive/databox-export-destination. Should it be restored from me-box-archive? It's more of a debug tool, so if so, not sure if it should have the platform prefix like platform-app-store.

To dockerise, the app store's Dockerfile without line 8 and 10 should suffice.

mor1 commented 7 years ago

I'd prefer that all the infrastructure necessary for a databox install, or for the demo apps etc, was installed and running under collective control rather than a single individual.

What is it actually used for currently?

If it's containerised, can run it here alongside the forum pretty easily I think.

On 20 October 2017 at 19:53, Yousef Amar notifications@github.com wrote:

Should be very quick to deploy on any server. Pure Node, no native deps: https://github.com/me-box-archive/databox-export-destination. Should it be restored from me-box-archive? It's more of a debug tool.

To dockerise, the app store's https://github.com/me-box/platform-app-server Dockerfile without line 8 and 10 should suffice.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/me-box/databox/issues/161#issuecomment-338293248, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKP4LQuh9-N0rZqCalTtA0kVvrp_p9Gks5suOw6gaJpZM4P-mL5 .

-- Richard Mortier mort@cantab.net

yousefamar commented 7 years ago

AFAIK currently os-monitor and the twitter demo app export to that URL. Perhaps if it was an optional dev mode component that could act as a local placeholder for apps that want to export, it will have served its use? Sort of how the local app server is done? (@Toshbrown what do you think?)

If we use it for demos, as we are now, then I think it would be better if it were just a one-off thing. It logs all requests no matter where they come from, so it's no good if many people export to it at the same time for general debugging. I can't quite remember, but perhaps that was the reasoning behind archiving it (after all, for debug you can just tail -f apache/nginx/whatever logs).

yousefamar commented 7 years ago

Otherwise, if we wanted to turn it into a debugging tool (e.g. export to export.databoxproject.uk to test before you launch your own server), then I think it would need to be extended to have some kind of namespacing or authentication, such that the requests can be divvied up by source databox / dev.

Toshbrown commented 7 years ago

I would prefer export.databoxproject.uk over another remote service running locally. But am happy to be convinced otherwise.

The export service could be altered to embed an identifier into the exported data to use as a filter. As a quick and easy fix.

Toshbrown commented 7 years ago

@mor1 Also might be worth moving the app server too (after Mozfest). Currently, it's running on toms server at store.iotdatabox.com.

mor1 commented 7 years ago

Agree. I've created a tracking issue at #165. We'll revisit after Thursday.e