Last post May 10, 2019 06:58 PM by bruce (sqlwork.com)
May 10, 2019 02:44 PM|InspiredJide|LINK
Hello so I have got a Web application built on asp.net Core. This web application is meant to be deployed for smes in my location.
I am trying to create a friendly installable process that is similar to wordpress framework. Remember when a user wants to deploy wordpress. He simply picks the wordpress folder and deploy in wamp www. From there is given a set up process which includes
database name, username, password. e.t.c.
I am trying to do the same thing for my asp.net core web application. So users who want to deploy dont have to be editing the appsettings.json file.
With a GUI form. I can just enter server IP, database name, username and password with port.
With that my system just updates the json setting file so setup process is not that technical.
So I am looking for best ways to read and write to the appsettings.json file from my html form and controllers.
I am open to suggestions if there is a better approach to fix this problem.
May 10, 2019 05:51 PM|bruce (sqlwork.com)|LINK
is there a common web server your smes are deploying to? if their own box, are you using IIS or core self hosting. if self hosting do they just run on demand?
where are they deploying from? a shared folder, GitHub?
May 10, 2019 06:01 PM|InspiredJide|LINK
I would be deploying to their own box. I strongly believe I should core self hosting on their own box.
So the application is suppose to automate their sales process. Which is their daily activities.
So the reason why I want it flexible so I can reduce the need of too much technical support.
May 10, 2019 06:03 PM|InspiredJide|LINK
And does asp.net core run on all windows OS. Am just curious cos some systems out there might still have windows 7 running on it.
May 10, 2019 06:58 PM|bruce (sqlwork.com)|LINK
see supported os for core 2.2
you will need to decided if the user must install core support, or you will build a self-contained release.
you will probably need at bat file to run the application. you could easily pass the config setting via the command line, and have deployment build the bat file with the proper settings.
if you want the web application to have a setup page for config, then I'd use a separate config file for user customized settings.
note: this does not appear to be the most user friendly approach. run a app and then use a bowser to connect to the app. even if the bat file starts the browser, if they close it or navigate away, they need to reconnect. also a cmd prompt window will be
open that runs web application. if they close the cmd windows, the core app will exit.