Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Maintenance mode #17

Closed
sedubois opened this issue Oct 3, 2016 · 2 comments
Closed

Maintenance mode #17

sedubois opened this issue Oct 3, 2016 · 2 comments

Comments

@sedubois
Copy link

sedubois commented Oct 3, 2016

It could be useful to disable HTTP access to a project similar to Heroku, for example:

  • to do some bigger backend refactoring
  • if an issue comes up (endpoint compromised, permission rules mixed up etc)
  • simply to put a project "in the fridge" for a while
@sedubois
Copy link
Author

Just a comment that I would still find it helpful to have this. E.g right now I'm building a backend whose access needs to be controlled, but there is no authentication system in place yet. So I'd need an easy way to disable access to the backend when I'm not doing the development. Right now I go to the permissions and disable all the permissions one by one.

@marktani
Copy link
Contributor

This issue has been moved to graphcool/graphcool-framework.

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

No branches or pull requests

4 participants