Location of myServer data directory

retate's Avatar Topic Author
User User
  • Posts: 64
  • Thanks: 1

Location of myServer data directory

2 years 7 months ago
#492
The Lutron Caseta instructions state to copy  the Integration Report to "myServer 6's data directory.. Where is the data directory located? 

Please Log in or Create an account to join the conversation.

David Li's Avatar
Admin Admin
  • Posts: 1027
  • Thanks: 99

Re: Location of myServer data directory

2 years 7 months ago
#498
/home/allonis/applications/myServer/data
on the myServer controller. Access this via a HDMI monitor and mouse / keyboard.

Please Log in or Create an account to join the conversation.

Re: Location of myServer data directory

2 years 7 months ago - 2 years 7 months ago
#500
There is no Home/Allonis on my rasp pi

I found /usr/local/Allonis
Last edit: 2 years 7 months ago by graydon@gdsamps.com.

Please Log in or Create an account to join the conversation.

David Li's Avatar
Admin Admin
  • Posts: 1027
  • Thanks: 99

Re: Location of myServer data directory

2 years 7 months ago
#502
Hi Graydon, that's because you are on the 32 bit Master Image as part of the Alpha group.  The Kickstarter group has the new 64 bit build.
32bit users it's here "/usr/local/Allonis/myServer/data"

Please Log in or Create an account to join the conversation.

Re: Location of myServer data directory

2 years 7 months ago
#504
Oh, thanks. Well, now I feel like a second class citizen! My machine is only 32bit. ;-)
-GDS

Please Log in or Create an account to join the conversation.

Re: Location of myServer data directory

2 years 7 months ago
#506
I was just looking for this because I was trying to figure out if I could share my gdstheatrephone.html with Tom who is trying to get the JVC driver to work on his JVC projector. Maybe he could change the IP address and try my file to see if his projector responds.

Is there an easy way to share resources like that? I could see sharing macros too.

Thanks,
Graydon

Please Log in or Create an account to join the conversation.

Time to create page: 0.282 seconds