hernandito

Community Developer
  • Content count

    1041
  • Joined

  • Last visited

Community Reputation

6 Neutral

About hernandito

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. How about creating a new cache-only share. Move the files into this; then add this share as one of your media locations in kodi or plex, or whatever you use.
  2. Best bet is to install the node js stufff into amazon lambda account, then create an Alexa skill also on amazon. stuff is not easy for us tinkerers.
  3. Works like a charm. I can go to the Dockers screen and refresh to see as Dockers come online. thank you!
  4. Don't understand about the VPN. As I said my Dockers take ages to start. If I'm the only one w this issue, please ignore my OP. I can certainly wait a few minutes until the CLI. But in my case it's quite long. I am going to give Squid's suggestion a try. Thanks guys. H.
  5. Thanks guys. I have a couple of homemade Dockers that go through a long install every time. I think I have a total of 22 Dockers. The he cli is available. Any chance of monitoring this process from there? @jonathanm it's a nice idea, but I can see me forget to start the array, and the be stuck far away and not be able to start it.
  6. It would be great to be able to pull up a web page that shows the booting progress of not just unRAID, but of the loading of Dockers and VM's. For me, it is safe to say that upon a reboot, after I get the login prompt (on monitor connected to server), it could be like 15-20 minutes before the web ui finally loads. Obviously it's waiting to load all the Dockers and VM's. Some indication of what is happening would be useful. Please consider this as a measure of substantial stress relief during that time when one could think something has gone wrong with our precious server. Many thanks, H.
  7. Dude, what an awesome lifestyle. Wish I had that free spirit and the courage to live those adventures.
  8. Not sure how to resolve your issue. You could try to run this command from your unRAID CLI. Switch out the username/password with the correct ones. docker run -d -e GOOGLE_EMAIL=steve@stevegattuso.me -e GOOGLE_PASSWORD=[password] -e APP_URL=http://alexa-geemusic.stevegattuso.me -p 4000:4000 geemusic Remeber that the APP-URL has to be a valid internet URL to your server from outside your network. If you do not have that, there is no chance this will work. Plenty of tutorials out there how to do this.
  9. sounds like you did not enter your email or password properly... when I added mine, the error went away.
  10. Try this xml... Create a file in /flash/config/plugins/dockerMan/templates-user/ and call it my-geemusic. Paste the below contents into the file and save. Then install it and fill out the info. My docker was able to log into my google account. Beyond this, I cannot help. <?xml version="1.0"?> <Container version="2"> <Name>geemusic</Name> <Repository>kuroshi/geemusic</Repository> <Registry>https://hub.docker.com/r/kuroshi/geemusic/~/dockerfile/</Registry> <Network>bridge</Network> <Privileged>false</Privileged> <Support>https://hub.docker.com/r/kuroshi/geemusic/</Support> <Icon>http://i.imgur.com/glans3o.png</Icon> <Overview>A bridge between Google Music and Amazon's Alexa [b]Converted By Community Applications[/b]</Overview> <Category/> <WebUI>http://[IP]:[PORT:4000]</WebUI> <TemplateURL/> <Icon/> <ExtraParams/> <DateInstalled>1497043160</DateInstalled> <Description>A bridge between Google Music and Amazon's Alexa [b]Converted By Community Applications[/b]</Description> <Networking> <Mode>bridge</Mode> <Publish> <Port> <HostPort>4000</HostPort> <ContainerPort>4000</ContainerPort> <Protocol>tcp</Protocol> </Port> </Publish> </Networking> <Data/> <Environment> <Variable> <Value>place-your-email-here</Value> <Name>GOOGLE_EMAIL</Name> <Mode/> </Variable> <Variable> <Value>yourpassword-here</Value> <Name>GOOGLE_PASSWORD</Name> <Mode/> </Variable> <Variable> <Value>address-from-outside</Value> <Name>APP_URL</Name> <Mode/> </Variable> </Environment> </Container>
  11. It is there, but there is a big missing issue... creating the SSL certificate in your server/docker/reverse proxy, and tie it to the skill. You may know more about the subject than I do, but just from experience, it has never been as straight forward as the guides suggest. Using the Heroku may be slightly easier, but then there is no docker needed as Heroku is hosting your skill. I believe it costs $$. You can also have Amazon Lambda host the code for you (free for a ton of requests per month). But I saw nothing on the git on how to do that. He talks about ngrock, I have never tried or seen that. Perhaps that is the answer. I'll take a look and see how easy it would be to create a template for their Docker, but after that, I am positive I will not know how to actually make it work w/ Amazon. I dont have Google Music either.
  12. Hi Furtive, Creating stuff to work with Alexa is not a simple matter. While it can be simple to install a Docker and have it run what is needed, it get complicated when you get to the Amazon side of things. You need certificates in order to connect to your server to/from Alexa. You need to create the skill in your own Amazon account. I have tried many times to get Sonos, and Kodi Alexa skills to work with very little success. I am not a pro, but also not a newb either. I do hope for more unRAID community interest for Alexa fans. I would love Couchpotato, Sonarr, Raddar, Medusa, Sickrage, Kodi, etc. Alexa connect dockers. Something that perhaps integrates LetsEncrypt certificates... So.... +1 from me. This is part of the Amazon side of the skill setup:
  13. Sorry guys, I have not kept up with this Docker. Last time I tried it, I was using another Docker fork. This is how my config page looks like: A quick install shows it running... Cannot recall which template I use for this. But I git this from my /config/plugins/dockerman/templates-user/myMy-MineOS.xml Just make sure you edit the "XXXXX" with your own password- in two places. <?xml version="1.0"?> <Container version="2"> <Name>MineOS</Name> <Repository>yujiod/minecraft-mineos</Repository> <Registry>https://registry.hub.docker.com/u/yujiod/minecraft-mineos/</Registry> <Network>bridge</Network> <Privileged>false</Privileged> <Support>http://lime-technology.com/forum/index.php?topic=39623.0</Support> <Overview>&#xD; MineOS is an easy to manage Minecraft Server. It has its on web interface to manage all aspects of the server.[br][br]&#xD; [b][span style='color: #E80000;']Directions:[/span][/b][br]&#xD; [b]/var/games/minecraft[/b] : set this path to where you wish all the Minecraft Server items to be stored. Should be you app folder.[br][br]&#xD; [b][span style='color: #E80000;']IMPORTANT - Open Advanced View to Set your PASSWORD!!![/b][/span][br][br]&#xD; </Overview> <Category>MediaServer:Other</Category> <WebUI>https://[IP]:[PORT:8444]</WebUI> <TemplateURL/> <Icon>http://i.imgur.com/P6RRtHH.png</Icon> <ExtraParams/> <DateInstalled>1485459269</DateInstalled> <Description>&#xD; MineOS is an easy to manage Minecraft Server. It has its on web interface to manage all aspects of the server.[br][br]&#xD; [b][span style='color: #E80000;']Directions:[/span][/b][br]&#xD; [b]/var/games/minecraft[/b] : set this path to where you wish all the Minecraft Server items to be stored. Should be you app folder.[br][br]&#xD; [b][span style='color: #E80000;']IMPORTANT - Open Advanced View to Set your PASSWORD!!![/b][/span][br][br]&#xD; </Description> <Networking> <Mode>bridge</Mode> <Publish> <Port> <HostPort>8444</HostPort> <ContainerPort>8443</ContainerPort> <Protocol>tcp</Protocol> </Port> <Port> <HostPort>25565</HostPort> <ContainerPort>25565</ContainerPort> <Protocol>tcp</Protocol> </Port> </Publish> </Networking> <Data> <Volume> <HostDir>/mnt/cache/appdata/minecraftos4/</HostDir> <ContainerDir>/var/games/minecraft</ContainerDir> <Mode>rw</Mode> </Volume> </Data> <Environment> <Variable> <Value>XXXXX</Value> <Name>PASSWORD</Name> <Mode/> </Variable> </Environment> <Config Name="Host Port 1" Target="8443" Default="8443" Mode="tcp" Description="Container Port: 8443" Type="Port" Display="always" Required="true" Mask="false">8444</Config> <Config Name="Host Port 2" Target="25565" Default="25565" Mode="tcp" Description="Container Port: 25565" Type="Port" Display="always" Required="true" Mask="false">25565</Config> <Config Name="Host Path 1" Target="/var/games/minecraft" Default="/mnt/appdata/minecraftos/" Mode="rw" Description="Container Path: /var/games/minecraft" Type="Path" Display="always" Required="true" Mask="false">/mnt/cache/appdata/minecraftos4/</Config> <Config Name="Key 1" Target="PASSWORD" Default="minecraft" Mode="" Description="Container Variable: PASSWORD" Type="Variable" Display="always" Required="false" Mask="false">XXXXX</Config> </Container>
  14. Thank you NASty! I will definitely give it a try...
  15. Hi Guys, My Windows PC is running really slow. I installed a VM for Mint and it installed and seems to be working fine. I assigned it 8 cores and 12GB of Memory. When I start it, I get the below message in the log screen. Does this mean that it is NOR running optimally? If so, any idea how to resolve? Many thanks, H.
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.