►
From YouTube: hyper TSC meeting 10-4-2021
Description
In this meeting, the hyper core team reviews the roadmap for the next month and shows the hyper cloud dashboard and its feature flag functionality as well as talks through the authentication workflow.
Want to learn more about hyper, join our community - https://hyper.io/slack
A
Okay,
so
today
is
october
5th,
it's
hard
to
believe
that
it's
october
5th
there's
a
lot
that's
been
going
on
and
since
our
last
meeting,
here's
kind
of
a
quick
set
of
goals
that
we
hit
in
september
we've
been
building
and
designing
the
application
tier
for
hyper
cloud,
including
graphql.
A
The
core
business
rules
are
complete
and
we
continue
to
complete
the
dashboard
functionality.
Last
two
weeks
ago
we
had
a
product
launch
planning
session
and
really
reduced
the
initial
release
to
a
developer
preview.
A
Maybe
tripp
can
show
some
of
that
in
a
little
bit
and
then
the
other
two
bits
that
we
worked
on
or
focused
on
in
september
was
hyper
connect,
a
client
that
makes
it
easy
for
node.js
and
dino
to
connect
to
the
hyper
service,
whether
it's
running
locally
or
running
in
our
cloud
service
and
a
hyper
test
and
hyper
test
is
really
to
to
validate
hyper
adapters
in
an
end-to-end
test
suite.
A
So
we've
been
continuing
to
refine
that
and
basically
have
fully
tested
it
on
our
local
service,
our
nano
image
and
we'll
be
testing
it
against
the
cloud
images
shortly.
So
that
was
september
in
october,
probably
the
biggest
news
is-
is
we're
launching
the
developer
preview
of
hyper,
which
is
the
data
service
kind
of
free
tier.
A
So
the
plan
is
to
launch
the
data
service
and
free
tier
developer
tier
october,
18th
and
19th
that
all
things
open
and
then
we'll
set
up
a
roadmap
and
launch
additional
services
over
time
and
additional
tiers.
The
next
two
tiers
we
have
is
startup
and
agency,
and
then
the
services
that
we'll
be
releasing
is
cash,
storage,
queues
and
search.
A
So
those
will
all
be
coming
down
the
pipe
and
we
we
figured.
We
would
incrementally
release
so
that
we
can
help
people
on
board
and
really
create
some
good
quality
documentation
and
some
good
quality
workshops
for
developers
to
use
the
product.
So
that's
really
what
I
had
was
kind
of
to
show
our
current
roadmap.
A
You
know
what
we
did
in
september.
What
we're
looking
to
do
in
october,
also
looking
to
you
know,
get
some
open
source
contribution
with
the
dynamodb
adapter
and
then
at
some
point,
an
authen
or
a
scheduler
port,
and
our
goal
is
to
try
to
on
board.
I
think
50
developers
for
the
developer
preview
version
and
that's
it
for
me
trip
did
you
were
you
able
to
get
something
that
you
could
possibly
show.
A
B
All
right,
so
here's
the
this
you
know
the
home
splash
screen,
prompting
you
to
sign
in
you'll
need
a
github
account.
It
says:
welcome
to
developer
preview.
B
Once
you've
signed
in
you'll
see
your
applications,
we're
gonna
hide
some
of
these
features
behind
feature
flags.
So,
for
example,
you
know
we're
not
going
to
have
teams.
B
We're
not
going
to
have
payment
we're
going
to
have
the
data
service
available
to
you,
but
we're
going
to
release
the
cash
search,
storage
and
queue,
as
tom
said,
via
a
road
map.
So
if
I
were
to
refresh
this
now,
let
me
go
back
and
shut
it
down
start
back
up.
B
So
you
know
we
should
see
you
know
we
have
upgrade
true,
but
let's
turn
that
off
the
faults
right.
So
now,
if
we
go
back
upgrade's,
not
there
anymore,
it's
hidden
behind
a
feature
flag.
B
If
I
go
to
look
at
a
an
app
in
hyper,
we
just
see
the
data
tab
right,
but
when
tom
says
release
the
kraken
release
the
cash
service
or
whatever
service
we
want,
we
can
just
turn
that
on
and
boom
it'll
be
on
right
and
able
to
and
able
to
manage
that
so
right
now
you
know
we
don't
have
teams
on.
B
So
you
can't
add
a
team
or
see
teams
or
anything
like
that,
but
once
we
turn
that
on
you
know,
you
get
the
idea
all
of
a
sudden,
your
ability
to
add
teams
and
everything
else,
light
up
right
and
you
could
switch
over
to
a
team
and
add
an
application.
B
B
And
now
you
have
a
casey's
great
cash
service,
so
you
can
see
it's
it's
coming
along.
It's
a
lot
tighter.
We
moved
deleting
an
application
back
behind
a
kind
of
like
a
service
application
service
settings
where
we
could
delete
the
application
if
we
wanted
to.
We
haven't
implemented
that
mutation,
yet
to
do
that,
but
we
will
so
we
have
you,
know
kind
of
like
in-app
documentation,
links
where
you
can.
You
know
see
see.
B
You
know,
find
out
more
information
about
what
you're,
interacting
with
through
the
through
the
app.
So
that's
what
we
have
right
now
we
well,
we
also
integrated
with
with
stripe
as
well.
So
I
haven't
tested
that
in
a
while-
and
it's
not
going
to
be
there
for
for
the
developer
preview
but
I'll
turn
it
on
anyway
see
what
happens.
B
Why
not
so
I
could
go
and
if
I
wanted
to
create
a
new
team
I'll
call
it
super
friends.
B
Oh
lighter
instead
one
more
okay,
there's,
light
orange
and
I'll
create
a
new
team,
and
if
the
demo
gods
are
with
us,
it'll
pop
us
over
to
stripe,
so
we
can
there's
our
email
we
can
put
in
our
our
information
payment
information.
B
It's
not
real
casey,
so
don't
steal
it
and
then
subscribe,
and
then
that'll
set
me
up
with
a
paid
hyper
startup
subscription
for
that
team.
B
So
that
application
was,
it
should
have,
should
have
popped
up,
I'm
so
sad
that
application
should
have
two
services
with
the
data
in
cash
created
for
you
so
pretty
easy
to
use.
So
you
got
to
see
teams,
you
can
see
payments,
you
got
to
see
apps,
creating
app
instances.
It's
coming
along.
B
B
We
just
have
like
a
feature
flags,
you
know
library
here
and
we
just
have,
it
is
feature
enabled
curried
function
and
we
just
build
little
constants.
The
boolean
values
that
we
export,
and
so
you
can
just
bring
those
into
your
app
and
you
say:
hey
is
this
enabled
then
show
it.
If
not,
then
don't
so.
For
example,
if
teams
are
if
teams
are
enabled
which
they're
not.
B
You
know
can't
see
teams
anymore
and
if
I
try
to
create
a
new
team,
I
forget
what
that
was.
I
think
it
was
teams
new.
I
think.
B
B
Yeah,
so
it
was,
it
was
pretty
easy,
so
I
would
highly
recommend
if,
if
you're,
if
casey,
if
you're
not
using
them
to
use
feature
flex,
you
could
release
darkly
and,
and
you
don't
have,
and
no
one
can
ever
use
your
features.
So
that's
that's
what
it's
all
about.
At
least
you
can
release
it
and
get
it
out
there
in
a
while
and
then
hide
it
turn
it
on
when
you're
ready.
E
Yeah
I
remember
reading
about
it
recently
and
I'm
actually
wondering
I
don't
think
that
I
I
was
reading
about
it
through
something
from
hyper,
but
I
don't
know
if
one
of
you
maybe
shared
it
in
chat.
I
remember
where
I
found
it
just
randomly
yeah
feature
flags,
look
very
cool.
B
Yeah,
it's
it's
pretty
straightforward.
It
was
surprisingly
pretty
painless
to
put
them
in,
so
we
purposely
kept
it
high
level
on
our
flags
and
not
getting
too
granular,
and
if
we
need
to
separate
a
ui
flag
from
a
back-end
flag,
we'll
just
put
a
is
ui
flag
prop
one
on
this
array
of
flags
but
yeah
anyway.
So
that's
that's
the
demo.
It's
tightening
up
from
the
last
time
we
did
it.
That's
cool.
A
Looks
looks
good
tyler
thanks
for
joining.
You
have
any
updates
from
your
and
hey.
F
Yeah
sorry,
I'm
late,
I
was
typing
up
an
issue
on
the
on
the
hyper
repo
and
I
lost
track
of
time.
Whatever
happens
to
me
so
as
as
far
as
far
as
demo,
I
don't
think
I
didn't.
F
I
didn't
prepare
anything
to
show,
although
I
have
been
pretty
busy
with
you
know,
working
on
hyper
cloud,
but
in
particular
the
conversation
that
you
and
I
had
tom
on
friday
that
auth
solution
that
we
needed
to
put
in
place
so
that
I
can
sort
of
describe
here
to
the
group
just
so
that
everyone's
aware
of
sort
of
how
this
is
working
so.
F
So
with
hyper,
so
with
hyper
cloud,
of
course
we
have
our
dashboard
and
for
those
of
you
don't
know,
we're
actually
dog
fooding
cloud.hyper
to
build
out
the
dashboard
and
everything
that
runs
the
dashboard.
So
how
anyone
else,
who
is
a
user
of
hyper
cloud,
can
have
an
application
inside
of
cloud.hyper
where
they
store
all
their
data
and
they
have
all
their
hyper
services
running
we're
doing
the
same
exact
thing
for
the
dashboard.
F
We
have
our
own
application
cloud.hyper
and
we
do
some
bootstrapping
when
we
do
some
bootstrapping
inside
of
cloud.hyper
to
spin
up
the
hypercloud
application
within
cloud.hyper.
So
so
part
of
that
is
a
part
of
cloud.hyper
is
when
a
request
comes
in
for
a
particular
app.
F
Cloud.Hyper
looks
at
that
token,
and
it
needs
to
verify
it,
and
so
cloud.hyper
itself
is
when
it
spins
up
it
also
bootstraps
a
set
of
services
that
it's
using
to
store
all
of
the
api
keys
that
it
provisions
for
accessing
services
on
cloud.hyper
or
applications.
I
should
say
it
will
take
that
token.
It'll,
look
at
the
sub
they'll
look
at
the
application,
that's
in
the
url,
and
it
will
fetch
the
api
key
pair
from
these
services
that
it's
spun
up.
F
F
I
probably
could
have
diagrammed
something
out,
but
I
did
not,
but
I
can
I'll
probably
throw
something
together
just
for
posterity
and
making
sure
that
we
are
clear
on
how
everything's
working
there,
but
it's
all
working
great
now,
and
so
basically,
the
hyper
cloud
dashboard
does
the
same
thing
where
anytime,
it's
serving
up
data
for
the
hypercloud
dashboard.
It
sends,
along
its
own
api,
key
pair
to
cloud.hyper
cloud
that
hyperverifies
it
and
then
it's
just
a
just
a
regular
old
consumer
hyper.
So.
A
F
C
Nicely,
and
did
you
have
to
have
a
kicker
to
to
kick
you
out
of
the
inception
loop
that
you
found
yourself
in
actually
there's
a
lot.
F
Of
there's
a
lot
of
white
boarding
involved
and
lots
of
like
like
charlie,
from
always
sunny
where
he's
standing
in
front
of
the
board.
With
all
the
yarn
everywhere
and
he's
just.
C
F
So,
but
that's
all
working
so
as
of
right
now,
like
all
the
authentication
stuff,
is
good
and
ready
to
go,
and
so
I've
just
been,
as
tripp
was
saying,
feature
flagging
all
of
the
stuff
on
the
dashboard
back
in
we're
using
graphql
and
so
feature
flagging
was
pretty
straightforward
for
us.
We
just
took
those
same
feature
flags
that
trip
created.
F
We
imported
them
into
where
we
stitch
our
schema
and
if
a
certain
feature
wasn't
enabled,
then
we
didn't
stitch
in
the
mutation,
the
type
and
the
resolver
for
the
mutation,
and
then
we
had
a
couple
types
that
we
omitted
from
our
graph
as
well,
but
with
that
everything's
pulled
out
of
the
api,
no
one
can
consume
it,
but
because
of
the
way
that
we've
set
up
that
that,
like
admin
graph,
that
I
was
showing
to
you
tom
and
tripp,
the
the
other
day,
we
can
omit
parts
of
the
schema
from
the
that
from
the
schema
that
the
from
the
graph
the
dashboard
consumes,
while
leaving
it
still
open
on
the
admin
graph.
F
If
we
wanted
to
do
that,
so
could
be
a
way
for
there
could
be
some
use
cases
there.
F
But
that's
what
I've
been
working
on?
Sorry,
that
was
a
bit
jumbled,
but
it's
been
busy
busy
busy
working
yeah.
I.
A
I
I
hear
that
we've
got
off
work
working
and
we're
not
having
to
add
a
bazillion
infrastructure
bits.
So
I'm
super
excited.
F
No
just
two
more
two:
more
a
hyper
data
service
and
a
hyper
cache
service
still
within
cloud.hyper.
A
Very
nice
and
benz
joined
the
call
benz
started,
you
know
kind
of
leading
our
comp
community
support
effort,
and
one
of
the
things
is
that
we've,
I
think,
got
almost
50.
A
Well,
I
know
we've
got
30
people
to
join
our
slack,
but
really
working
on
trying
to
you
know
open
up
our
our
slack
and
invite
people
that
are
interested
in
the
developer,
preview
and
ben
is
is
helping
us
kind
of
engage,
run
some
giveaways
and
really
just
reach
out
to
the
community
and
help
us
make
make
people
aware
of
hyper.
So
that's
pretty
awesome
ben
did
I
miss
anything
anything
you
want
to
add.
G
A
That
was
so
funny,
that's
kind
of
that's
kind
of
javascript
randomness
there,
where
it's
the
same
person
every
single
time.
A
A
Yeah
and
so
that
that's
going
on
and
casey
and
and
a
couple
of
guys
have
are
currently
looking
at
doing
the
the
dynamo
db
adapter
casey
any
updates
you'd
like
to
share
on
that
or
comments.
E
I'm
going
to
meet
with
them
fairly
soon
to
get
that
finished
and
squared
away.
I
met
with
a
few
students
last
night
and
just
went
over
some
dynamodb
stuff,
including
included.
A
But
yeah
so
just
start
on
that
yeah,
yeah
and,
what's
pretty
exciting,
is
you
know,
been
kind
of
slow
going,
but
I
think
we've
got
a
good
starter
template
for
kind
of
a
contract
and
a
statement
of
work
and
we
kind
of
structured
it.
As
a
you
know.
Each
kind
of
feature
has
kind
of
a
a
set
bounty.
It's
real,
really
kind
of
like
a
bounty
so
but
the
the
the
just
as
all
the
features
have
to
be
completed
in
order
for
everything
to
clear.
A
A
We'll
be
doing
more
of
that
in
the
future.
So
well,
you
know,
once
casey's
team
gets
rolling,
we'll
you
know
work
out
all
the
bumps
and
bruises
and
then
look
to
do
more
of
that
in
the
future.
So
so
I
covered
our
roadmap.
A
We're
going
to
be
at
all
things
open
in
october,
18th
and
19th
we'll
have
a
booth
and
a
virtual
booth
and
going
to
be
a
road
trip
to
raleigh.
So
it
should
be
fun
and
again
tell
all
your
friends
to
join
the
community.
It's
really
an
easy
link.
Now
it's
hyper.io,
slash
slack
that
should
send
them
to
the
invite
page.
So
it's
super
easy
to
sign
up
and
that's
gonna,
probably
be
the
best
place
to
you
know,
find
out
what's
going
on
with
hyper,
so
that's
all
I
had.
A
Does
anyone
have
anything
else
before
we
close
out
great
work
trip
great
work,
tyler
ben,
thank
you
for
helping
us
with
the
community,
because
I
don't
think
we
could
focus
if
we
had
to
do
that
too.
So,
thank
you
very
much
and
yeah.
Thank
you.
Ben.
D
A
All
right:
well,
thanks
everyone,
great
work
and
we'll
see
you
next
month.
E
Yeah
so
you've
got
free
tier
and
then
you
jump
to
startup,
which,
if
I
recall,
is
around
400..
If
you
guys
considered
a
in
between
like
a
developer
tier,
that's
like
ten
dollars
a
month.
If
you're,
I
imagine
like
a
private
developer
with
a
personal
site
or
something.
A
Yeah,
it's
a
great
question,
so
our
goal
is
to
make
the
free
tier
the
developer
tier,
that's
the
initial
goal,
but
if
you
know
if
there
is
a
need
for
like
a
single
developer
to
because
because
essentially
what
you're
getting
is,
is
business
support
so
five
days
a
week,
you
know
kind
of
nine
to
five
support
with
the
the
paid
tier
so
yeah.
I
think
I
think
we're
definitely
open
to
that.
But
right
now
we're
just
trying
to
keep
it
kind
of
simple.
A
But
we
do
have
the
flexibility
in
the
code
base
to
kind
of
slice
it
in
any
way
that
it
makes
sense.
So
technically
it
you
know,
I
I
should
default
to
tyler
before
I
say
something,
but
I
believe
technically
we
would
be
able
to
carve
out
another
tier
if
we
needed
to.
F
Yeah
yeah
yeah.
We
can
definitely
the
flexibility.
Is
there
like
to
create
another
tier
to
have
one-offs,
for
particular
customers
like
if
a
particular
customer
wanted
an
additional
app
or
an
additional
service
within
an
app
that
should
all
be
supported
by
our
current
business
logic,
and
you
know
making
those
sorts
of
exceptions
to
the
sort
of
sort
of
the
rules,
but
then
adding
a
whole
other
tier.
That's
also
possible.