I have looked extensively through SO, but have yet to find any help with this question, despite trying almost every recommendation.
https://github.com/danwaz/powerhour
trying to install this app on Spotify. I do have a developer account, and have created the necessary dir in ~/documents/Spotify
For whatever reason, I am shown a loading bar when I attempt to load the app according to how the manifest details the bundle. I do get a "metadata started" message, but nothing loads...it just sits there spinning its' wheels.
Any recommendations from anyone?
What platform are you on?
If you're on a Mac or Linux, the folder should be ~/Spotify, where ~ is your home directory.
If you're on Windows, it should be in the Spotify directory of your My Documents folder.
Related
I made an application with Next.js and used node.js in the api part. I had no problems using it on my own computer, but when I run it on my server in digitalocean, the photos I uploaded from the administration panel are not shown. When I check the database and directory, there is no problem. The photo is being recorded there. section is correct when I enter the site and check it. When I wear path / file.jpg it gives 404 error.
There is no problem in the previous recordings and it shows the photos. The photos do not show after running on the server.
I made folder permissions 777, but nothing else came to my mind. I didn't add code because I didn't think there was a problem with the code.
I solved the problem as follows: It started to work after defining express static files into the API.
I would be most grateful if anyone could help me solve this problem with ClickOnce Web deployment.
I have read all the threads on this subject and I have also read through all the Microsoft documentation on the subject. They seem to say a lot without actually being direct or providing helpful examples. However, perhaps I am wrong and I have not looked in the right places.
I have already used ClickOnce successfully to deploy an application on the local area network.
It works well and really isn't that complicated. However, my goal is to deploy this application to customers, who are not connected to my local network.
I have set up a web site (www.mydomain.co.za), which I can access directly or via the ftp protocol.
I have created a sub directory off the root where I intend to publish the files created by the publish function. The publish function of the application requires a Publishing Folder Location and a Installation Folder URL I don't really understand the functional difference between these two locations. If I set the Publishing Location to ftp://www.mydomain.co.za/MyProductName and the Installation Folder URL to http://www.mydomain.co.za/MyProductName, then the publish process succeeds and when I check on the web server, the files have been published successfully it would seem. A further Application Files/MyProductName subdiectory with the version number information appended was created where all the output was placed.
My next step is to then grab the URL of the setup.exe file and to run it from a browser. This downloads the setup.exe file to my downloads folder which I then try to run but I get an error
Deployment and application do not have matching security zones.>
I have seen this come up in other threads but These threads don't seem to relate directly to what I am trying to do. These threads make mention of using Internet Explorer to achieve some degree of success, but all the browser did was to download the file.
I have also noted with interest that a web page is created in the root with a button that prompts the user to install the application. This does not work either.
Does anyone know of an article that I can read on this subject which is more helpful or if anyone can offer more insights into this I would be very grateful.
I need a service application in Firefox OS which should start at boot time. I searched several sites but didn't get anything useful. Also I would like to know what all changes should be made in the manifest file and js file. Also the requirement of index.html file.
There is the Background Services, but it's not available yet, and tagged a certified app right now. So it's not possible at the moment.
The most relevant API that could act as 'service' is alarm API, which allow app to trigger itself periodically and do some stat checking. Calendar/Email App use that technique to pull new event/mail from internet.
Ref: http://tech.mozilla.com.tw/posts/2223
I'm building a launcher for internal use with a Chrome packaged app which includes links to internal resources (databases, web links, etc.).
The problem is with local files. I want them to launch using whatever program is the default handler for them. For example, access databases open in Access, etc.
I've tried:
Creating a file link file:///. Nothing happens in this scenario on click and the link is not followed.
I found an extension (locallinks) here: https://code.google.com/p/locallinks/, which will open local file links. I've tried borrowing from that extension and passing the file link to the background script in my packaged app which would then open a new window with that url. Unfortunately, that results in a file not found, even for simple types such as text files. So obviously the local filesystem is sandboxed. Not surprising.
I thought maybe it would work to pass the link to an extension to open, but in that case, the file would be opened in Chrome and if Chrome does not support it, it would attempt to download the file locally.
The reason I'm using Chrome Packaged Apps is:
1. This will be updated often and the Chrome Web Store update feature would make it easy to keep clients updated without having to build our own update mechanism.
2. We can restrict installation of the app through CWS to internal users.
3. The app would be used in a Windows, Linux and Mac environment. Obviously the file paths here would be different but since they would point to a samba share, and mount points and network share drive's are known this is an easy problem to overcome.
4. There is additional functionality we will be building into the Chrome app in the future other than the launcher which fits very well with how Chrome Apps are designed.
My thoughts are:
Native Client? I have read a bit about these, but I think I would end up with the same limitations where the native client app would be sandboxed and may not actually have any better way of launching a local file.
Sockets? Maybe a simple Qt app listening on a socket to launch apps? Since the Qt app would be run with user permissions, and the socket would only accept connections from localhost, I guess the socket could in theory be used by a non-privileged app to launch something with user-level permissions. Is there a way for me to limit connections through the socket to only be accessible from my extension?
The sockets solution isn't ideal but may work since the app would not be updated often (if ever) since functionality is so simple.
Am I missing an obvious way of doing this that wouldn't require another component (a Qt app?)
Relating to your thought #2, not sure what local installation footprint you are willing to tolerate, but you may consider:
Hosting a miniscule local web server, or Qt app as you mention, which can also launch local programs (any of those lightweight web server frameworks). Have your packaged app, or your own chrome extension rewrite links such that they point at your web server along with the url of the original link, which can easily launch whatever program. Downsides: this may cause bypassing some browser security screening of the original links in some forms of implementation.
You may also look at this stackoverflow question if it helps.
You can limit access by confirming the requests originate from the local machine, or by embedding a key or hash inside your chrome extension. You may generate the key upon installation so that it's unique per machine. None of this will pass very proper security scrutiny so it depends on your risk profile. You will have a hard time justifying how each part is secure and clean of exploitation attack potential.
It seems you will need both a chrome extension and a local miniscule web server to make this work. Maybe it's easier to let users just download the files and click them...
Sorry if this isn't help enough, but basically you are trying to do something that is by design not made possible in Chrome, so at this state of affairs there would likely not be a simple solution.
My development account for Spotify has been enabled and I am trying to walk through their simple tutorial app (http://developer.spotify.com/download/spotify-apps-api/tutorial/). I should note here that I am on a Win 7 workstation.
When I try to load the local app by typing 'spotify:app:Tutorial' in the search field I get the following msg/error: "Sorry, I could find this app. metadatafailed URI: spotify:app:Tutorial Error: appNotFound."
I have tried adding the app files to the following directories and still getting the error:
C:\Users\Me\Documents\Spotify\Tutorial (note this dir did not exist I created it)
C:\Users\Me\AppData\Local\Spotify
C:\Users\Me\AppData\Local\Spotify\Users\me-user
C:\Users\Me\AppData\Roaming\Spotify
C:\Users\Me\AppData\Roaming\Spotify\Users\me-user
So where exactly are you suppose to add the files so that Spotify will load local apps?
Thanks!
Your first guess is correct (C:\Users\Me\Documents\Spotify\Tutorial). However you need to be running the latest preview release (https://www.spotify.com/uk/download/previews/). And on my PC I had to completely un-install and reinstall the application before the developer options became enabled.
Not sure whether it helps in your case, but try naming the folder tutorial with lowercase t. See Spotify Tutorial example app is blank
I can't leave a comment, but I was having the same issues and had to do a combination of what Niklas and akakjs did. I had to completely uninstall the spotify app, download/install the preview version, create a Spotify directory in My Documents, then create the folder Tutorial. Then, in the Spotify search bar I had to type "spotify:app:tutorial" with the lowercase t. I hope this helps!
Had the exact same problem. I had to run Spotify as administrator, worked right away.
And the path i used were: C:\Users\me\Documents\Spotify
I had the same problem: Spotify could not find my app directory even though the proper folder had been created in my Documents folder.
I Fixed it by running Spotify as an Administrator.