►
From YouTube: Speed run for Generic Package Registry
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
we
are
working
on
having
a
new
type
of
package
registry
called
generic,
and
it's
basically
generic.
You
can
push
any
random
file
under
some
packets
with
name
and
version
and
then
download
it,
and
that's
usually
something
that
package
will
work
on,
but
we
we
started
because
we
want
to
use
it
for
release
generation
so
that
you
can
be
able
to
generate
your
release.
Assets
then
push
them
somewhere.
A
If
you
don't
have
like
where
to
push
them
right
now
and
then
use
the
urls
in
your
in
when
creating
releases,
and
it's
still
working
progress
and
I'm
trying
to
keep
it
pretty
simple
for
now.
So,
basically,
that's
a
project
that
doesn't
have
any
packages
right
now.
I
will
need
to
do
a
front-end
course
request
or
generic
here
on
the
top
separator
and
the
way
you
upload
is
you
just
make
a
put
request
to
the
api.
A
A
That's
the
the
end
point
where
you
have
like
the
project
id
it's
here.
Then
you
have
the
package
name
package
version
which
I
kept
simple
for
now,
just
the
major
minor
parts
from
same
version
because
it's
easier
to
validate
and
if
we
decide
to
have
a
latest
endpoint
later
it's
easier
to
sort
in
the
database
and
that's
the
the
file
name,
but
it's
similar
to
what
other
packages
are
doing
right
now
and
this
will
actually
the
actual
upload
will
be
accelerated
in
workhorse.
A
So
yeah
I'm
basically
adding
another
route
that
when
workhorses
are
out
like
this,
it
hijacks
the
equate
request,
uploads
the
package
to
like
local
disk
or
object
storage.
If
it's
supported
and
then
then
it's
passing
the
the
data
for
that
file
to
rails,
so
that
all
this
happens
faster
and
it's
not
overloaded
dealing
with
uploads
and
let's
try
to
actually
upload.
A
A
If
we
go
back
here,
yeah,
that's
my
awesome
package
version,
one
zero
0
and
here
is
the
file
which
you
can
download
so
yeah.
That's
basically
it
I'm
now
working
on
the
upload,
the
what
I
just
showed
it's
in
in
review
and
then
we
will
have
one
more
merch
request
for
downloading,
because
it
doesn't
make
sense
to
just
upload
stuff.
You
can,
if
you
can't
fetch
it
and
that
will
be
like
the
mpc.
We
need
for
release.
Generation.
A
B
A
B
A
Yeah
so
for
c,
we
support
the
common
package
manager
and
that
this
is
a
generic
ui.
We
have
for
packages
and
it
just
works.
I
haven't
done
any
front-end
work.
It
just
works
by
adding
the
records
to
the
database,
but
for
all
of
these
package
types
we
have
a
separate
database
tables
to
keep
the
metadata,
because
it's
different
and,
for
example,
for
column.
A
We
have
even
maybe
more
than
one
table
and
if,
if
I
had
a
column
package-
and
I
you
click
on
column,
then
you'll
see
all
the
additional
stuff
around
this
and
it's
same
for
maven
and
npm,
and
you
get
in
the.
A
D
So
my
question
was:
we
have
a,
we
have
a
section
where
we
show
releases
right.
Yeah
is
this?
Would
this
like?
Is
this
intended
to
integrate
with
that
in
some
way,
or
is
this
intended
to
be
just
completely
separate.
A
I
think
it
will
be
separate
and
in
releases
when
you
create
a
release,
you
can
grab
the
you
can
use
the
user,
the
download
url
for
this
file
and
then
just
use
it
as
a
asset
link
when
you're
creating
the
release
so
they'll
be
separate,
because
some
people
may
actually,
for
example,
why
I
was
just
when
I
started
working
on
this.
Someone
was
asking
on
slack
that
one
of
the
windows
distrust.
I
think
it
was
arch
linux.
A
It
has
a
pretty
simple
package
like
system
and
it's
just
a
zip
file
and
you
just
need
to
be
able
to
push
it
somewhere
and
download
it.
So
then,
this
generic
packages
can
be
used
as
a
package
register
for
arch
linux
or
it's
basically
like
whatever
it's
kind
of
like
s3.
You
can
push
and
pull
stuff
from
it
and
it
has
some
versions
and
that's
it
so
yeah
at
least
to
answer
your
question.
I
don't
think
we'll
integrate
them
now,
but
we'll
just
use
the
links
from
the
package
registering
as
a
release.
Asset
links.
D
Okay,
that
makes
sense.
This
is
a
this
is
like
a
really
cool
building
block,
because
I
can
see
a
lot
of
just
sort
of
like
with
a
generic
thing
like
this.
You
could,
you
can
build
on
top
of
it
and
all
sorts
of
things,
yeah.
A
That's
that's
that's
one
of
the
in
the
issue
in
the
epic.
We
have
that's
one
of
the
reason
we
have
it,
because
our
use
case
is
just
one
of
them
and
you
can
use
it
as
a
substitute
for
other
registries
that
we
don't
support
yet
or
for
something
else,
and
it's
offered
the
same
feature
is
being
offered
by
the
competition
like
jfrog
and
nexus.
They
they
all.
They
have
like
some
sort
of
like
just
raw
packages
or
generic
packages,
kind
of
yeah.
C
And
then
oh
yeah,
I
was
gonna
say
no,
I
think
one
of
the
most
requested
features
we
release
is
attaching
binaries
or
things
that
are
related
to
that.
To
that
release,
and
by
having
this
we
can
just
create
a
even
though
it's
just
a
link
that
is
going
to
point
to
this
to
this
package
registry,
but
at
least
it's
going
to
be
somewhere
and
then
in
your
release.
You
can
just
click
and
download
and
it's
all
good.
D
A
Okay
and
yeah
so
last.