Creating a Startup Support Crew

[noire.munich]

@keith.t.elliott

Reach out with a specific time when you are ready.

Thanks a lot @keith.t.elliott will do!

@thedavid

@noire.munich Really excited for you! And so very much appreciate how you’re also helping make Redwood better via your contributions + feedback. Lots of things below.

Thanks a lot @thedavid , I’m really happy about it! And happy it’s something we can make happen together.

More below

Version bumps

@thedavid

• if we could figure out a way to turn around patch releases more quickly (e.g. v0.27.1), would that give you more confidence to stay current with Redwood versions?

Definitely!
We talked about it this morning, we’re willing to stay current with RW’s versions and synchronize with Redwood core team on upgrades.

So, we’re on board with this, we will follow the current RW versions. We are open to provide access to core team members to our github, it could help us both on identifying which side should work on a fix, if ever necessary.

@thedavid

^^ oh, man, you’re going to what’s coming in v0.28 I’m telling you, it’s going to be painful for you to wait.

Not waiting anymore only sad we won’t have time to have fun with every new stuff each release :D.

Prisma

Here’s what our PO got, he installed the project a couple of weeks ago and we followed standard heroku db creation. Well at least old standard, maybe we’ve missed something in recent updates.

 yarn rw prisma migrate dev
yarn run v1.22.5
$ /home/florent/PycharmProjects/sportoffice/node_modules/.bin/rw prisma migrate dev
Running Prisma CLI:
yarn prisma migrate dev --preview-feature --schema "/home/florent/PycharmProjects/sportoffice/api/db/schema.prisma"
Prisma schema loaded from db/schema.prisma
Datasource "DS": PostgreSQL database "dbq7iv1ncjm1t3", schema "public" at "ec2-108-128-104-50.eu-west-1.compute.amazonaws.com:5432"
Error: P3014
Prisma Migrate could not create the shadow database. Please make sure the database user has permission to create databases.  More info: https://pris.ly/d/migrate-shadow. Original error:
Database error: Error querying the database: db error: ERROR: permission denied to create database
   0: sql_migration_connector::flavour::postgres::sql_schema_from_migration_history
             at migration-engine/connectors/sql-migration-connector/src/flavour/postgres.rs:192
   1: sql_migration_connector::sql_database_migration_inferrer::calculate_drift
             at migration-engine/connectors/sql-migration-connector/src/sql_database_migration_inferrer.rs:40
   2: migration_core::api::DevDiagnostic
             at migration-engine/core/src/api.rs:100
error Command failed with exit code 1.

Not sure about it but I’ve got a vague recollection that @rob mentioned we could opt-in shadow db use in 2.17, is that accurate? During the 19th of Feb. meetup, chat messages.

Storybook

Done here #2064

Schema modelisation

@thedavid

^^ Curious if you’ve shown them the GraphQL Playground?

No, but we discussed it. They are not reluctant but it would mean dedicate time so the PO could learn some GraphQL - that’s not feasible right now nor for the coming months.
Prisma has been working on something for a while apparently but there are no news about it. We’re ok not having diagrams for the schema if we can browse one for the API, which GraphQL Playground doesn’t help with much - unless we use it to export the schema to https://apis.guru/graphql-voyager/. That one, actually, could help the PO and the associates navigate through the data structure.
Our IDE supports diagrams generation w/ yFiles product details, that’s basically what we’d need, but I’m not sure it’d be Redwood friendly.
These are the two leads I’d digg into, to find something that would get us closer to that goal while being a Redwood addon. There are other leads but they are either not free or cloud-based only. I’ll keep in touch if we find something else.