getting VIP list to show on index page #34

Open
johnhitz opened this Issue Aug 18, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@johnhitz

On pg. 45 after entering the erlang shell with erl -pa ebin and reading the record via rr(visitors_db). I had to do a 2>cd(".."). in order to get the visitors file to be in the root directory. When I did not cd directory in erlang all the commands work in the shell but the visitors file is placed in the /site directory. When I then add the get_visitors/1 function to visitors_db.erl it creates a new empty visitors file in the root which causes no names to show up in the VIP list.

@choptastic

This comment has been minimized.

Show comment
Hide comment
@choptastic

choptastic Aug 18, 2015

Collaborator

Thanks!
On Aug 17, 2015 10:24 PM, "johnhitz" notifications@github.com wrote:

On pg. 45 after entering the erlang shell with erl -pa ebin and reading
the record via rr(visitors_db). I had to do a 2>cd(".."). in order to get
the visitors file to be in the root directory. When I did not cd directory
in erlang all the commands work in the shell but the visitors file is
placed in the /site directory. When I then add the get_visitors/1 function
to visitors_db.erl it creates a new empty visitors file in the root which
causes no names to show up in the VIP list.


Reply to this email directly or view it on GitHub
#34.

Collaborator

choptastic commented Aug 18, 2015

Thanks!
On Aug 17, 2015 10:24 PM, "johnhitz" notifications@github.com wrote:

On pg. 45 after entering the erlang shell with erl -pa ebin and reading
the record via rr(visitors_db). I had to do a 2>cd(".."). in order to get
the visitors file to be in the root directory. When I did not cd directory
in erlang all the commands work in the shell but the visitors file is
placed in the /site directory. When I then add the get_visitors/1 function
to visitors_db.erl it creates a new empty visitors file in the root which
causes no names to show up in the VIP list.


Reply to this email directly or view it on GitHub
#34.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment