Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Single points of failure #2

Open
buhman opened this issue Jan 31, 2018 · 3 comments
Open

Single points of failure #2

buhman opened this issue Jan 31, 2018 · 3 comments

Comments

@buhman
Copy link

buhman commented Jan 31, 2018

Isn't the API server a single point of failure? What does this claim mean?

@paulogr
Copy link
Owner

paulogr commented Jan 31, 2018

Hi @buhman thank you for asking.

No, it isn't.

There's a lot more to talk about it, but when you start up the service the api server is only responsible to serve the client (admin interface) you use to publish the incidents on IPFS network.

So the admin interface served on port 7200 it's not suposed to be open to the world.
The IPFS gateway (port 8080) hava access to the IPFS network and hold you files.

Give it a try, follow the instructions and publish a single incident them click on View your status page on Dashboard screen.

@paulogr
Copy link
Owner

paulogr commented Jan 31, 2018

I'm working on a more detailed spec of how to use this software.

Please follow for updates.

@buhman
Copy link
Author

buhman commented Jan 31, 2018

I think admin interface availability and being able to guarantee the currently displayed public page is up-to-date is probably more important than the availability of a historical version of the status page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants