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

Maintenance mode #11

Open
marktani opened this issue Jan 22, 2018 · 1 comment
Open

Maintenance mode #11

marktani opened this issue Jan 22, 2018 · 1 comment

Comments

@marktani
Copy link
Contributor

Issue by sedubois
Monday Oct 03, 2016 at 07:03 GMT
Originally opened as https://github.com/graphcool/prisma/issues/17


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
@marktani
Copy link
Contributor Author

Comment by sedubois
Thursday Apr 27, 2017 at 20:22 GMT


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.

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

No branches or pull requests

1 participant