From this tutorial https://daattali.com/shiny/persistent-data-storage/, I learnt that it is not possible to store data locally on shinyapps.io
Since the responses are saved locally, this can only be used if you have access to the machine hosting the app and if you trust its filesystem. If you don't know what machine the app is hosted on, or if the files could get deleted, do not use this method. This approach will not work if hosting on shinyapps.io because of those reasons.
Is this also the case for the premium accounts? I did notice, that you can actually store data locally during the session, but cannot access it after the session close. I assume it's deleted then.
Is the same for premium accounts, and by design. The machine hosting your app can change from one session to the next, and in such case your data will be missing.
Related
I am currently using Windows hosting for my Android app, from a local Domain provider.
I have developed and published my app on the Firebase platform. I want to know if moving (the hosting) from current Windows hosting to Firebase will make the app respond faster?
firebase surely will respond faster as it use ssds as and seperated server cdn to reach user in global but it's just the server that cached and optimezed for faster respond it's depend to your code for threading the process for more tricky performance :)
Why are ASP.Net membership credentials stored in a database not portable between (1) web apps and (2) machines?
Two scenarios --
We backup the production database and restore it to the development server. None of the production login credentials work on the development server, even though the underlying data was restored from production seconds before.
We build a new version of the app ("v2," let's call it), and install it on the production database under a different website (alongside the production app -- "v1"), but talking to the same production database. None of the login credentials work on v2 of the app, even though it's talking to the same database and therefore has the exact same membership data.
There is no machine key in the web.config file. If I leave this out, I assume it bubbles up from the machine.config file, which means it should be the same per machine, which means the two webapps talking to the same database on the same machine (the second scenario above) should share credentials, correct?
We also checked the application names and IDs in the databases, and they are identical between machines.
If you reset the passwords, everything works fine (with new passwords). But that means everyone has to reset their passwords, which isn't ideal.
It seems that somehow, the password salt changes from database server to database server and from web app to web app.
Edit:
Using ASP.Net 4.5 and System.Web.Security.SqlMembershipProvider 4.0.
Another Edit:
I have verified the PasswordFormat is "Hashed." Additionally, I have checked the Password and PasswordSalt fields between the two databases. They are identical.
Solution:
The hashing algorithm in the web.config was set differently between the two apps.
The hashing algorithm was different between the two webapps. One was using the default "SHA1," and the other was explicit set to "HMACSHA512."
I have an existing ASP.NET website that I would like to port to Azure within my free trial.
I would like the migration to be as painless as possible. The application uses log4net and NHibernate, plus it needs to share data with an application supposed to run on a virtual server.
Two questions can be asked as 1
How do I configure paths in Web.config to access a shared drive?
I need to configure the paths into which logs will be stored and, most important, I have to specify where the application will read the files written by the daemon that will run on my Azure Linux VM.
When both the app and the daemon ran on the same server (yes, I had Mono running fine) I just had to choose a shared local directory.
I'm not sure I'm totally understanding the scenario, but I'll try to give you a few options.
One - Windows Azure Web Sites (currently in Preview) could be a great option for your ASP.NET site. Of course, it depends what needs your site has. But, you can write your log4net files with web site and using NHibernate too.
Two - Web roles work great for situations like this. You would likely have to change some code to use blob storage for persistant file storage. You could use Windows Azure drives as a way to get a persistent location for log files. Windows Azure drives don't have a pre-determined drive letter, so you'd want to use the API to get to that. That may, or may not, be a good option for your situation. With web roles you could also write the log4net files to local storage and use Windows Azure diagnostics to transfer them periodically to blob storage. Just another way to persist the files.
Three - Using Windows Azure Virtual Machines (currently in Preview) you could write the log files to a data disk, which is backed by blob storage.
In the end, if you have files you need to share across instances and/or roles, then leveraging blob storage is likely your best option.
We are hosting our web application over azure. Everything went well so far with a web role of only 1 small instance.
We then decided to try out 2 x extra small instances for our web role so that http requests will be load balanced.
Our session is also stored using the MS recommended method found here .
When we published on the production environment, the session work well (being filled an all). When testing it locally on the azure emulator, the session just wont be filled.
Anyone know what might be the problem? Thanks!
The problem was due to the local firewall. Turning it off made the cache available for session state!
My local machine is using windows application for an appointment fixing. I want to retrieve data from webserver DB which also does appointment fixing by online for the same organisation. So I want both these to work in co-ordination. As my first step I want to import data.
What problem are you having or concerned? Are you concerned about the concurrent use of the database and date entry, or are you concerned about possible duplication of work?
Also, why do you need a Windows application when you already have a web app? What platform is the Windows application written in (.NET, Win32)?