I have a chess app which can load and save chess records (PGN files) via Dropbox. The Dropbox access permission was all folders (which was popular in the old days). Recently, many users are writing to me for their concern of letting a chess app to access all Dropbox folders. So I am going to limit my app to a single app folder, i.e.: inside a Dropbox/Apps/Chess folder.
The question is, what is the proper way for the my app to migrate files from other folders to this Dropbox/Apps/Chess folder? As I will switch Dropbox API key during the process, how can I minimize the trouble for the users.
Related
I'm developing a Web Application, and it is running as an Azure Web App. This application has a section in which a user can navigate a directory, and allows the user to open the files and browse sub-directories in said directory.
At the moment, the sub-directories and files are inside "~/Content/Documents", and I am browsing the directory's by using Directory.GetFiles() and Directory.GetDirectories(); functions which are provided by System.IO.
The files in question would be retrieved and downloaded several times a day, and there is no way to manually path one-by-one, seeing as there is a large quantity, and they are subject to change.
However, I has become inconvenient to store the files within the web directory. So my two questions are:
What Azure service can I use to store and retrieve my files?
and
Which of these services provides the ability to index/map a path, which would fit with my web-app?
Please note that the users do not have the ability to edit or otherwise upload any of the files, and there is therefor no need for the service to allow non-authenticated upload.
The newish Azure File Storage feature can be used to store files in Azure Storage and make them accessible via an SMB file share. This will allow for legacy application that require the use of a traditional file share for saving / retrieving files. This allows for easier integration into existing applications without needing to completely rewrite the file storage code.
https://azure.microsoft.com/en-us/blog/azure-file-storage-now-generally-available/
I have two web application in my solution. One of them is for managing the system and another is for clients.
I should publish them one by one in separated places (of course on a machine but in separated addresses for Example http://manager.com and http://clients.com)
My question here is that, can clients web application access the files that the other manager web application has (in its physical directory)? If not how can I approach this problem?
see this design to get more details for this problem :
Thanks!
What I usually do in a scenario like this, is store the files in a folder in the application that does the writing. Then I use IIS to create a virtual directory in the other application that points to the folder containing the files in the first application.
So in your case, you could have a folder "Files" in the manager.com website. Let's say the folder has this full path: D:\Websites\manager.com\Files You can then create a virtual directory in the clients.com website pointing to that path.
This has the advantage that you can code everything as if the folder exists in both applications.
If your applications placed on one machine - certainly can.
You should do only one thing - give permission to folder with files (Or permission to DB with files) to user that run your web application on web server (Usually IIS if you use MVC < 5)
It seems from your comment that you want to share uploaded files between multiple web project. You can store them in a common folder outside your web project folder.
For example, create a folder in
"C:\Temp\" say "SharedFiles".
The manager web application that receives the file from user (through upload) can store the files in this folder. The client web application can refer this location for file while reading.
You may have to give permission to the user (IIS_IUSRS) to access this folder.
I recently had my application rejected, by Apple for:
"Your app has the UIFileSharingEnabled key set to true in the Info.plist, but files and folders not intended for file-sharing are contained within its Documents folder..."
I am storing my application data in the documents directory, images and the core data database. This is a very simple progress, that allows the user to backup and import data. Below are the major steps:
The user can backup the data, which zips the folder.
The user can then use iTunes file sharing to take out the backup.
The user can import, the zip file which overwrites the data in the documents directory.
Has anyone else experienced similar issues? It seems like I am using this correctly.
You should put the zip file in the Documents folder, not any other files. The fact that you also put your core-data files (and some of the other files the user shouldn't see) in the Documents folder is why it was rejected.
You can store any files that the user shouldn't see in another folder such as the Application Support folder.
I am trying to develop an app which will retrieve a list of files and folders inside a specific Dropbox folder (from a user-specified folder). What would be the best way around doing this? Possibly some code snipplets if possible as I am still new to Rails.
I'm working on an iPad app which is deployed manually from iTunes. The app requires a large amount of data (videos). The data is static, the app is being developed. It is inconvenient to deploy all the data each time the app is deployed.
What are my options to deploy the application itself separately from the data?
Use iOS file sharing to get the files into the Documents directory for your app. The documents directory will be preserved across upgrades as you develop the app, so you only have to copy it once.
If there's a lot of files, you can copy a zip file instead and unpack it on the first run of your app using SSZipArchive.
Another option would be to stick the data on a web server and retrieve it on the first run, again storing it in the Documents directory.
If you want to use any of these approaches in your final deployed app, be sure to make the files so that they're not backed up to iCloud.