I am very well known for site deployment on Heroku server. But I only see how much memory used in my server. I can not see my files.
Related
I have a local PostgreSQL Database for my Discord Bot on my PC and want to update to my Heroku Application. I have added the Heroku Postgres Addon, but don't know how to upload the Database. I can't use the Amazon Web Services as told in the devcenter since i don't have any Credit Card. Is there any way to upload the Database without AWS? Thank You and sorry for my bad English
You can dump your local database contents to a SQL file with pgdump. Then you can access your Heroku database from your local machine and upload your SQL using the psql command-line client. Get the access url like this from the Heroku command and put it into your client program.
heroku config | grep HEROKU_POSTGRESQL
Know this: sometimes Heroku migrates your data from one host machine to another. When they do that they change your access url. So retrieve that url again whenever you use the psql client.
I have a flask app connected to a local postgres db with SQlAlchemy for dev purposes. I also have a live version of the app running on Google App Engine which is connected to a postgres db on CloudSQL
I am trying to use flask-migrate (which builds upon alembic) to manage database migrations. I can run the migrations fine locally but I am unsure how to manage the migrations for the deployed version?
this answer
has a couple of useful answers. One suggesting getting an IP address and being able to connect directly but I don't know where I would use that URI for migrations?
The other answer suggests running the code as an endpoint in the app itself.
Any pointers would be greatly appreciated
in my workplace we have setup a django web app on staging server running frontend and on production server running frontend , the frontend is a UI for deploying projects . however recently I was pointed out that staging server should not be using the production database. That makes complete sense. However the staging server beside just for testing the changes made also serves as a failsafe as runs on docker based apache server and docker runs on different machine. so if something is wrong we are able the developers are able to make use of staging server for publishing there softwares meanwhile my team fixes the production server. But the frontend of staging server as well is connected to same database as the production (as it is required for developers to be able to use staging server as failsafe)
So my question is does sharing database between web apps running on staging and production can cause an issue ? how it should be handled ?
With my personal experience, if your database host is powerful enough, you should be fine. I've had zero problems doing what you mentioned above. People quite possibly consider it a security concern since there will be more bugs/exploits in your staging web app where an attacker could access your database and affect your production web app. But that's only a worst case scenario.
Some of the Google App Engine documentation make reference to the term "development server". What is a development server? Besides development server, what are the other types of servers?
Is abc-def-123.appspot.com on a development server? If it is, how do I deploy to a non-developmental server? Is it just by Enable Billing in the Developers Console ?
The development server runs locally and allows you to run your AppEngine application entirely on your local machine during development. Other "servers" are the AppEngine production servers where you deploy your application when it's ready.
You use the gcloud tool for such tasks.
When the app runs on a development the application id gets a dev~ prefix.
I am a newbie with DotNetNuke and have been stumbling on how to deploy from the development server to the deployment server. For starters my development and deployment servers are one and the same machine. Here are the steps that I did:
DNN Setup
Downloaded DNN using WebMatrix.
Launched DNN and proceeded with the installation wizard, which is basically just testing the environment and then creating the DNN database.
After the wizard's installation launching DNN will now proceed to the Getting Started page
Added "localhost/dnn" in the site alias list
Moving to ISS
In IIS I added application (folder) DNN in the web root
I copied all the files from the original webmatrix path to the dnn folder in c:\inetpub\webroot making sure that the file/folder hierarchies are the same
Result:
When launching DNN using my browser I am directed to the installation wizard page instead of the Getting Started page. What am I missing?
Thanks!
Confirm that the permissions on the folder containing DNN are the same on your test server as they are on your development server. (I give Network Service read/write and IUsr Read/Execute)
Confirm that the application pool running your application has the proper identity (Network Service is suggested) and is running the proper .NET Framework version; based upon your question, I think you are set on this.
Gain access to your web.config file. You will see a ConnectionStrings section. You probably need to update the connection strings.
If your test server runs off of a different database than your dev server, figure out the connection string of your test server and update your connection string accordingly
You may be able to restore a .BAK file of your DB to your test server
If you do this, you will probably need to (in SSMS) edit your Portal Alias table to include the host name that you are using in your test server environment. Examples: Maybe you access the site via localhost/ on your dev environment, but you access to test site via test.Ronald.com? test.Ronald.com would be your PortalAlias
If your test server runs off the same database server as your dev server, it sounds like you need to open up access in firewalls so that your test server has connectivity to your dev database
A word of advice
Once you get it running, you will be making changes to each database separately (assuming your test site and dev site use different DB Servers). This sync issue can be a royal pain with DNN, as your page structures, module assignments, html module contents, installed modules/extensions will get out of sync. While restoring backups is nice, it is not a very good long-term solution. I recommend database-syncing tools
The problem is most likely a problem with DNN not being able to find the Database. If it can't find the database, it will run the wizard in order to create one.