I have made a web application using R Shiny and deployed it with the shinyapps.io using the free mode. The problem that I have is that my application generates a set of .txt files which I need to download them after my application finishes. Is there any way that I can access those generated files? I have seen my shinyapps.io control panel, but I did not find any way to have access to my files.
Can I use Filezilla or a similar tool to have access to those generated files?
Related
I'm developing an asp.net web API, the functionality of the API depends on saving files, in my older projects i used to save files base64 string in SQL database, but currently I am trying to save them as files on the server and save the URL in the database, I am using iWebHostEnviroment with the root directory to save files in it, it works fine. My Question is if this is the right place to save them, i have never deployed API on server before so I am afraid that it's working only locally and after deployment it won't get the right directory on the server it self
I tried webHostEnvironment and HostEnviroment and all the returned paths are local paths on my pc, idk if this would work on actual server or i should save them somewhere else in the project
Is there a way to get access to the raw code of an application hosted on Shinyapps.io. I hosted my shiny application on shiny apps and made multiple changes in my code in my system. I need the older version of my app which has been hosted.
How about downloading it from the dashboard?
Please, note that you'll receive an extensionless file in the archive. Just add .tar to it, and you'll be able to open the file as an archive, as it was mentioned here.
I have an ASP.NET WebForms application which I would like to publish to a Web Deploy package and deploy using the deploy.cmd script generated as part of the Web Deploy package. This basically works fine but I have one problem.
My application generates image files which are stored in a temporary directory as part of the web site (basically a subdirectory of the IIS site's physical location called temp). However, whenever I deploy my site using the deploy.cmd script, this directoty is deleted. Instead, I would like the deploy script to make sure the directory is present and that the IIS user has access to it. Is this possible to do with Web Deploy out of the box?
I can easily write an asp.net code. I hit the visual studio RUN button and I see my website in Chrome or any other browser. But how do I do this without visual studio? I don't get an exe file, only the dll. I think, this must be copied somewhere.
Idea is to run (any) programm, which causes a special page to show my website (with OPC-data) on a local computer. Like an exe file.
To give more detail: I want to run some Web site code in a CEF (chromium embedded framefork) so that it looks like a normal executable. It will run only on a local computer (in fact a machine). This is static. But some information have to be provided dynamically by an OPC client. This will be read with VB and displayed via ASP.NET. The first application reads the data via AJAX. So I think what I need is some kind of local server (like wamp) which has to be started in the background. I found a batch file to start WebDev.WebServer40.exe. But this could not be the right way. A batch file sounds like stone age.
-->c:\Program Files (x86)\Common Files\microsoft shared\DevServer\10.0
You have IIS Manger installed, yes? If not, you can go to Control Panel \ Programs and Features and turn this Windows feature on. From within IIS, find the Default Website node and underneath that create a new application (this way it inherits the correct permissions). Point the application's start path to wherever your web app lives on your hard drive (the root folder that contains your app's web.config file). Anyway, that's one way to deploy your app locally.
So I'm using visual studio 2010 to build a website that was formerly running on PHP, so I'm pretty new to the environment.
In starting the project I built a website project, not a web application project. I know that will probably generate a lot of "never use a website project, use a web application project instead" comments, but bear with me.
I'm attempting to provide our server team with the necessary files to compile on our server for the first time. However they're used to working with web application files, not website files.
Normally they are given the source code and a batch file that compiles the code into deployment directories and then they just move the files to the server from there. I'm pretty sure that the other teams use deployment packages to do this, which obviously isn't an option for a website.
My question is, what would be the equivalent steps for getting the source for a website ready to deploy vs a web application? I have published the website to a separate folder and this has rendered what I think is the equivalent in many ways, but I wanted to make sure.
Also, is it possible to publish certain parts of a website without others?
Please with-hold all the comments about how I should be using a web application instead, google seems to assume that's all that's used out there too.
Thanks!
There isn't much to deploying a web site other than copying the source files to a directory in IIS. It will compile the site automatically on the first page request.
I agree with Britton. I personally prefer web application but with the web site project you have 2 options.
Either a) Upload all the files (including the .vb or .cs files) and the web server will compile on the fly. OR, you can publish to a separate folder locally on your machine, and then upload that folder. I would do the publish if you don't want anyone seeing your source code.