►
From YouTube: Zeus IDE: Easy Web-Based Development on EOSIO & DAPP Network (Blockchain Dev by Peter Keay)
Description
Advanced Blockchain Development Tools is an Everything EOS course sponsored by Cypherglass. Please vote for my sponsor! https://cypherglass.com
In this lesson, we intro the Zeus IDE, a powerful online Gitpod Integrated Development Environment ready to build EOSIO dApps with DAPP Network services.
NOTE: Gitpod will ask you to register and pay a subscription after 100 hours of use. You can, of course, instead continue development from your repository using a local environment.
**IN THIS VIDEO**
00:50 Getting Started
04:12 Creating a new contract to start from
05:36 Using DSP HQ to view your local state
06:39 Running your frontend
08:03 Forking to your own repo
10:51 Collaborating with others
**More Everything EOS Developer Videos**
Learn more about EOSIO and DAPP Network development by visiting our Everything EOS Developer Series Playlist:
https://www.youtube.com/playlist?list=PLRK9ZLYOWiXPJ2ThcTpn4e9Y6MyqqY49r
**GETTING HELP**
Stay tuned for updates on this course's learning platform launch! For now, follow the playlist and reach out to the Everything EOS telegram or https://twitter.com/bitgensteinx with any issues or questions.
Sign up for occasional updates at https://everythingeos.io/dev
Take the first course, which teaches the basics of building a smart contract and dApp frontend in ReactJS+Redux+NodeJS and C++, at https://www.udemy.com/course/eos-blockchain-dapp-development-tutorial
A
Everyone-
let's
have
no
and
do
on
this
one
we've
got
Zeus
SDK
we've
already
learned
how
to
set
it
up
in
another
video.
Maybe
you
struggled
through
that.
Maybe
there
were
issues,
maybe
you're,
working
on
an
iPad,
a
Raspberry
Pi.
This
is
the
video
about
Zeus
IDE
and
an
integrated
development
environment
that
you
don't
have
to
download.
You
don't
have
to
setup.
A
You
don't
have
to
run
it's
all
online
and
in
your
browser,
we're
gonna
figure
out
how
it
works
right
now,
so
pull
up
a
browser
and
from
wherever
you
are
go
to
get
pod
dot.
Io
forward
slash
little
hashtag
here,
github.com
forward,
slash
liquid
apps,
io
ford,
slash,
zeus,
ide-
and
this
will
take
this
repository-
that's
at
the
skin
hub
location
and
run
a
development
environment
there.
So
here
we
go
get
pod
is
starting.
A
I
might
want
to
turn
my
brave
shields
off
for
this
website
now
you're
going
to
need
to
login
with
a
github
account.
If
you
don't
have
a
github
account,
go
ahead
and
make
one
this
little
box
gets
lower
and
lower
def.
The
larger
you
make
the
text
a
funny
side
effect
of
of
how
CSS
works
so
anyway,
it's
gonna
be
pulling
some
images.
Setting
everything
up.
This
might
take
about
five
minutes
to
spin
up.
A
In
total,
an
integrated
development
environment
will
come
up
where
we
can
write
our
code,
where
we
can
test
things
where
we
can
view
previews,
where
we
can
open
up
a
helpful
chain,
Explorer
all
sorts
of
goodies.
Alright.
Here
we
are
in
the
Zeus
IDE
now,
hopefully,
unless
you're
running
on,
like
a
phone
you'll
have
more
space
than
I.
Do
I've
pumped
up
the
text
for
you,
so
that
you
can
see
things
a
little
better,
so
we've
opened
up
a
problems
bar
down
here,
no
problem.
A
So
far
we
have
no
Dios
running
in
another
terminal,
another
tab.
Here
we
are
Zeus
unboxing
dap,
which
is
a
box
that
has
all
the
various
services
you
could
possibly
want
to
integrate,
and
then
we
have
a
list
of
our
open
ports.
You
can
actually
open
previews
right
here
or
we
can
open
them
up
in
another
tab.
So
we
have
powerful
capabilities
for
interacting
and
viewing
with
what
we're
working
on.
Well.
It's
unboxing
all
the
stuff.
You
know
it's
unboxing
testing
frameworks,
all
the
dab
services
ipfs.
A
This
probably
looks
very
familiar
to
you
if
you've
used
integrated
development
environments
on
desktop
like
vs
code
Visual
Studio
code
over
here,
we
have
an
explorer
pump
this
out
a
little
bit
in
that
that
folder
this.
This
is
where
we've
unboxed
dap
here,
there's
all
the
stuff
we're
going
to
be
working
on
in
our
contracts
and
eventually
in
our
front
end
folder
as
well.
Once
it's
done
unboxing.
We
should
see
that
over
here
you
can
interact
with
github.
Of
course
you
need
to
do
some
some
stuff
here.
A
First,
so
let's
say
I
wanted
to
merge
some
changes
from
here
and
then
actually
create
a
pull
request
here
up
here,
I
have
my
github
avatar
and
various
things
I
can
do.
I
have
generally
the
functionality
you
would
expect
from
an
integrated
development
environment,
including
a
bunch
of
edit
ability
and
find
in
a
whole
set
of
files,
and-
and
there
are
no
downloads
involved,
I
don't
have
to
deal
with
any
setup.
A
Except
for
this
initial
wait
time
which
we're
looking
at
right
now,
you
only
have
to
do
it
once
unless
you
close
the
window
and
some
interesting
services
going
on
here
with
Tron
web
stockfish,
ripple,
Lib
and
Bitcoin
core
being
installed,
there's
just
so
much
going
on
with
es
J's
scatter
J
s
transit.
That
we've
got
a
lot
to
get
going
here
and
in
the
future.
You
can
actually
work
out
this
repo.
You
can
get
rid
of
the
compile
step
or
you
can
remove
the
compilation
or
whatever
for
services.
You
don't
need.
A
You
can
customize
the
tests
yourself
and
make
it
right
for
you
and
the
services
that
you're
going
to
be
using
all
right.
We
are
done
which
is
fantastic.
We
have
a
command
line
down
here
now
no
dias
says
killed,
but
you
can
verify
that
es
is
in
fact
running
locally,
and
now
we
have
a
front-end
folder
here
with
our
main
front-end
in
main
for
this
sampled
app
and
we
could
actually
do
Zeus
create
contract,
as
it
says,
Zeus
create
contract.
A
A
But
you
know
we
don't
have
to
actually
work
in
this
little
terminal
window
down.
Here
we
can
go
over
to
our
IDs
explorer
and
go
to
contracts
and
also
see
there
that
we
have
our
new
tutorial
contract
and
it's
ready
to
go
if
I
open
it
up
in
this
nice
tabbed
interface
I
see
that
it's
ready
for
vram,
it's
ready
for
liquid
log,
it's
ready
for
liquid
liquid
Oracle's
and
everything
related.
A
It's
ready
for
scheduled
tasks
accounts
the
liquid
lens,
read:
function
e
liquids,
V
CPU,
including
some
sample
stuff
for
testing
a
schedule
for
dealing
with
V
accounts
and
for
working
with
vram.
Let's
see
what
else
we
got
here,
we
got
some
token
stuff
that,
from
cold
token,
very
cool,
very
cool,
all
ready
to
go
to
customize
to
implement
these
services
in
your
DAP
from
right.
Here
now,
there's
actually
a
very
cool
add
on
that.
Dsp
HQ
has
enabled
one
of
our
adapt
service
provider.
A
Dap
network
portals
the
description
of
how
to
do
it
is
on
es
in
boxes
medium,
but
it's
get
pod
preview,
the
URL
and
then
specifying
the
network
to
be
local.
So
let's
go
get
pod
preview,
DSP
HQ
down
I,
oh
and
then
the
net
work
equals
get
pod,
URL
888
go
and
that
pulls
up
this
little
window
here
with
DSP
HQ.
A
You
can
actually
pop
it
out.
If
you
want
into
another
browser
as
well,
and
we
can
hope
we
could
change
networks
here
to
main
that
to
test
net
we
we
can
learn
to
do
some
stuff.
Just
these
are
links
to
various
liquid
apps
resources.
But
you
can
also
explore
blocks
here.
You
could
search
for
an
account,
including
V
account
support
on
your
local
development
environments
like
not
local,
but
your
your
local
get
pod.
A
So
all
these
functionality
for
exploring
what's
going
on
no
worries
you
can
check
it
out
with
DSP
HQ
and
now
I
want
to
actually
run
the
front
end
I'm
not
going
to
do
it
with
liquid
storage,
but
let's
run
front
and
main
oh
I
can't
do
it
from
there.
Obviously,
all
Zeus
commands
have
to
be
performed
back
up
in
the
main
box.
Folder
Zeus
run
front
end
main
see.
If
that
works,
it
says
front
end
is
listening
on
port
30
15.
A
Now
a
little
thing
should
pop
up
saying:
yep
a
service
is
listening
on
port
30
15,
but
is
not
exposed.
So
let
expose
that's
available
and
now
I
can
open
a
preview
of
my
front
end
or
open
it
in
a
new
browser.
Tab,
I'm
gonna
do
the
latter.
This
might
give
us
an
error,
but
you
should
see
it
tried
to
load
the
front
end.
There's
currently
an
error
in
this.
This
box's
front
end,
which
I'm
sure
will
be
handled
soon.
A
It
might
not
even
exist
by
the
time
you're
watching
this
tutorial,
but
if
you
can,
you
could
take
your
front
end,
which
is
in
the
front
ends
folder
whichever
front
end.
You
want
that
you've
built
here
and
just
pull
Zeus
run
front,
end
main,
and
it
will
run
your
front
end
for
you
and
you'll
be
able
to
interact
with
it
and
interact
with
the
local,
no
díos
through
your
smart
contract
that
you've
developed
in
contracts
yose
whatever's
in
there
now.
A
Nothing
you
do
here
for
now
will
be
saved
because
we're
working
on
the
the
cord
like
the
repo.
Let's
open
this
get
github
thing
here:
we're
working
on
liquid
apps
iOS,
Zeus
IDE.
We
don't
want
you
to
be
able
to
make
changes
to
the
starting-point
repo,
so
you
have
to
head
over
to
repos
here.
There's
several
ways
to
do
this:
you
could
also
hit
f1
and
search
through
these
handy
commands
that
git
provides.
It
says
you
don't
have
push
permissions
for
ID
juice,
IDE.
Obviously,
so,
let's
fork
this
repo,
a
little
thing
will
come
up.
A
Of
course,
it's
under
me
that
says
I
need
to
grant
permissions.
Get
pod
is
requesting
additional
permissions.
I
will
authorize
it
with
my
github.
Now
I
should
be
able
to
fork
all
right
up
here,
choose
to
create
an
own
fork
or
select
a
different
fork
for
below
fork
to
my
account
I'm
going
to
fork
it
to
my
account
successfully
forked
to
Vic
instant,
adjusted
the
remote
URL.
Now
I
can
go
ahead
and
take
these
changes
that
I've
got
if
I
go
over
here.
Let
me
drag
this
out
to
this
version.
A
Control
pause,
the
source
control
tab
this
one,
my
main
folder
that
I'm
working
on
here
and
stage
that
now
that's
staged,
ready
to
go
to
the
repo
right,
so
I'll
add
a
message.
Just
saying:
add
new
contract
and
I'll
commit
it,
and
then
that's
not
enough.
Of
course,
I
also
have
to
push
so,
let's
push.
So,
let's
change
to
bit
constancy
side
EE
over
there
change
to
my
new,
my
new
repo
right.
There
are
no
changes
because
I've
already
pushed
it
to
master.
A
A
This
folder
already
exists
because
I
have
tap
contracts
cos,
so
it
can
zhuzh
unboxed
app
there.
So
ideally,
you'll
make
additional
changes
to
prevent
this
from
happening
where
it
tries
to
unboxed
app
and
app
already
exists
and
all
that.
But
you
can
fork
into
your
own
repository
and
then
you
can
go
to
file
where
share
there's
a
share
here.
It
is
you
can
go
up
to
the
top
right,
where
your
user
account
is,
and
click
share.
A
Workspace
snapshot
to
send
a
snapshot
of
the
workspace
to
someone
or
share
running
workspace
sharing
running
workspace
will
give
me
a
link
that
lets
people
share
the
workspace.
However,
this
also
lets
them
commit
in
my
name,
all
right.
It
doesn't
share
it
and
they
log
in
with
their
own
github.
It
lets
them
commit
in
my
name,
so
it
it's
limited.
You
might
want
to
create
a
shared
github
in
that
case,
in
order
to
do
work
with
this
right
now,
there
might
be
better
solutions
that
I'm
not
aware
of
yet.
A
A
It
does
help
I'm
still
getting
used
to
it,
but
it
does
really
help
with
the
environment
issues
that
people
can
run
into
setting
up
on
their
machine
and
all
the
time
it
takes
in
general
to
set
up
an
environment,
and
there
are
a
lot
of
really
cool
integrations
and,
of
course,
this
integrated
development
environment
to
ease
the
development
process.
I
hope
the
hackathon
is
going
great
for
those
participating
and
I
will
see
you
all
soon.