graphile / graphile/graphile.github.io
Postgraphile Sandbox/Playground
Personne n'a encore pris cette issue.
- Langage dominant
- SCSS
- Étoiles
- 27
- Forks
- 126
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### Feature description
Make a new repo with a [Deploy to Heroku button](https://devcenter.heroku.com/articles/heroku-button) for easily playing around with postgraphile without having to install anything or do toilsome setup.
It should come with postgres, pgadmin and postgraphile installed and running within a docker container, probably with one or more example databases installed.
It should be running with a variety of recommended plugins and settings for development, like `--enhance-graphiql` and `--allow-explain`.
By default, it should run the CLI, but it should also have a JS-driven example included with a easy switch to use that, so you can fork, write a custom plugin, and deploy with a click.
(Note that it should not use heroku's built-in postgres because it doesn't allow CREATE ROLE and could get expensive if a malicious actor spotted a free, world-configurable database).
Inspired by [this discussion](https://github.com/graphile/persisted-operations/issues/6#issuecomment-822695546)
### Motivating example
1. Have one official playground running that prospective users can play with, to see what postgraphile is like in the wild. (This should probably be completely cleared and rebooted at regular intervals, perhaps with a bit of automation from the heroku api and a stable subdomain).
2. Allow postgraphile users to quickly spin up their own playgrounds to explore prototyping concepts.
3. Allow postgraphile users to to demonstrate a minimal repro case for a bug or issue by running DDL, inserting data, and running a gql query.
### Breaking changes
None
### Supporting development
I intend to build this myself over the next week or two, but who knows life happens sometimes, so I wanted to file as an issue in case I don't get to it and someone else wants to come along and build it.
I [tick all that apply]:
- [x] am interested in building this feature myself
- [ ] am interested in collaborating on building this feature
- [x] am willing to help testing this feature before it's released
- [ ] am willing to write a test-driven test suite for this feature (before it exists)
- [x] am a [Graphile sponsor](https://www.graphile.org/sponsor/) ❤️
- [ ] have an active [support or consultancy contract](https://www.graphile.org/support/) with Graphile
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par examiner la documentation de Heroku Button et la configuration basée sur Docker proposée dans l’issue, y compris les exemples de PostGraphile CLI et JavaScript. Le travail sera considéré comme terminé lorsqu’un nouveau dépôt pourra déployer un playground fonctionnel avec Postgres, pgAdmin, PostGraphile, des données d’exemple, les paramètres de développement recommandés et un moyen de passer à l’exemple JavaScript.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- docker, graphql, javascript, postgres
- Domaine
- backend-api-design, databases, developer-experience, devops
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100