I've got my laravel project deployed on heroku, I finally got almost everything working, I have the Procfile which changes the home directory, and my CSS doesn't give mixed content errors anymore.
I've set up a database with db4free.net, and set up the env file accordingly, I've also set up the heroku config vars as well.
Using the Heroku CLI I ran bash, and migrated, this did create the tables correctly. The issue I'm facing now is that when I go to register, it seems to have worked and redirects to the homepage, however the data is never entered to the DB so I cannot log in with these details.
I haven't changed anything to do with the registering code thats provided in the auth package.
So it WAS all working, Heroku and especially db4free are pretty slow at updating
Related
Finally i completed my first full project using server, client, data
i would like to know few things about how to host and upload full website include(server ,react, mysql)
i so wondering how that is work, for now i understand that to upload a simple website you need a domain and to hosting, just do npm run build and upload it..., this is something that i know but, when that is not just a simple website like
when i have such as
server side with Node.js + express that have requests (on localhost) *probably need to change the localhost to something else but what
Database running with MySql
React app that have many request to (localhost)
how can i hosting all of them and running my website for everyone, i mean that my sql will still running, CRUD Data will update normal, and the server will still get request and send or update them to mysql data.
and if I'll want to make some change on mysql, server, client
i want to change it like i change it now
Actually i'm not a FullStack developer if i don’t know it... 🥶 so i really interesting to understand all of that issues
i hope you guys havק An understandable answer for me, thanks 🙏 and just take your time :)
Well, where to start hehe. There are a lot of different ways to host a web app. Heroku for example makes this process really simple.
Personally, I use Digital Ocean to host my apps. This is generally how that goes:
I have a project with a folder structure that seperates the server logic and the client logic.
Since you're using Node, you build your client with npm run build. Next make sure the dist/build folder is inside your server folder. That is the folder you are going to 'host'. On Digital Ocean, you make a new droplet (which basically is just a tiny part of a server).
You install Node, Git, Pm2 and (for example) Nginx. You clone your project from Github to the server and install all the dependencies.
You have to do a few configurations with nginx (specifying a domain name for example) to make everything work. This article goes into more detail about that.
Also, a database is frequently hosted seperately. You should read more about that.
If you have everything setup, you can just code on your project as usual. Push new updates to github, and pull in the changes on the server.
Here is another post on Stackoverflow talking about hosting MySql with react.
I have built an e-commerce website on my local computer that uses Django version 2.2 and python 3.7.
The website consists of:
fancyfetish is the main project directory.
The apps, (cart, users, baseapp, products, blog) are all stored in their own directory 'apps.
Within the settings folder I have three settings files:
- production.py
- base.py
- development.py
The static file in the main directory is where I put collectstatic files.
Media is where I store externally uploaded images (product images for example)
Docs is just random bits like a hand drawn site layout.
Static files like JS and CSS are stored within baseapp, within apps.
I want to host this website on Amazon Web Services, and I assume I need to use Elastic Beanstalk. I went through the process of trying to host with free version of EB, installed the EB CLI, and after using eb create and eb deploy on the CLI my website appeared.
However, the static files didn't load properly in the first instance because I had not properly configured DJANGO_SETTINGS_MODULE. I have now done this. But before deploying I added eb migrate functionality so that I could also migrate my database.
This seems to have messed everything up. I can no longer deploy because there is a DATABASE error, which I expected. The error said 'Not able to connect to MySQL database through 'localhost'. Well, of course it cant.
So, in order to deploy my site on AWS I needed to configure the databases, because with the eb migrate functionality it will no longer deploy without trying to also connect to my database using the settings I have configured.
I have so far, whilst in development mode, connected my project to MySQL and everything is running perfectly on localhost, with my models transferring beautifully to the database just as I would like.
I worked out that I need to create a database on AWS, obviously. So I set up an RDS. I didn't link it to my deployed application because it would appear that the application doesn't have an environment that I can see when I log into my console. So where my project has been deploying to I don't know, because it doesn't look like the CLI version is connected to the online version in my console.
So I thought I'd deal with that problem later and work out how to make a database, which I managed to do. However, migrating the database I already have up and running on MySQL to my RDS database seems impossible, and there are not very good instructions. Let alone trying to then connect said database to my deployed application, which doesn't seem to sync with my local app.
So, I have ended up deleting everything because I was becoming so confused, with so many new directories (.ebextensions etc etc) and a database that wont connect, a project that won't deploy, a database that wont point to my project etc. I ended up created an EC2 folder and all sorts, getting myself massively confused with what I actually need to do to make this whole thing work.
If any part of this ramble makes any sense to anyone out there, and you yourself have managed to deploy a larger django project to AWS and keep your existing databases then please do let me know. But I have a feeling this may be a long shot.
Basically I need a step by step list of what to do to deploy:
For example:
1) Create an elastic beanstalk instance
2) Create an environment on CLI that syncs to the one in my AWS console
etc
etc
(With how to's if you possibly have the time!)
Thank you, and I am so sorry for being so confused by something that may be simple
Edited to show my process:
I have built a directory called .ebextensions with a file within it called django.config with the following content:
option_settings:
aws:elasticbeanstalk:container:python:
WSGIPath: fancyfetish/wsgi.py
I have run the following command:
eb init -p python-3.6 fancyfetish
There was no output as a result of this in the terminal, however a directory was created called .elasticbeanstalk with one file in it called config.yml
I then typed eb init to create an SSH key pair and there was no output from this command at all:
As you can see I have tried doing this several times.
Instead I created a key pair manually within AWS console and a file automatically to my computer called keyname.pem
I then typed into the console
chmon 400 path/to/key/keyname.pem
This provided no output on the terminal so I cannot know if it worked.
I moved the downloaded SSH file into the .SSH directory in the Home directory of my computer, and then in the terminal typed:
eb init -k nameofkey
The output was:
WARNING: Uploaded SSH public key for "fancyfet" into EC2 for region us-
west-2.
I then went on to type
eb create fancyfet-env
And an environment was created with the following output:
I know that this has to do with databases and connecting to MySQL.
I then typed:
eb deploy
With the following output:
So now comes the bit where I get stuck, successfully creating a database that connects to my already existing database that is populated with database in MySQL, and connecting the project to the database.
HELP!(Thank you so much!)
I have deployed a PHP website do an OpenShift PHP 5.4 Cartridge. The application loads just fine, CSS, JS, etc. but images do not load correctly. The images exist in the git repo which is being pushed to OpenShift just fine but when I attempt to access an image, say from http://someopenshiftapp/images/logo.jpg it fails with a 500 error.
The server log gives me:
/app-root/runtime/repo/images/.htaccess: Invalid command 'IndexIgnore', perhaps misspelled or defined by a module not included in the server configuration
I am trying to resolve this issue but so far google has not been able to help me. I tried editing the httpd.conf to include the module but that is a read only file. I may have to create a new cartridge from scratch? How do I serve images with OpenShift?
I don't know the exact reasons why Apache was behaving like this but it was. There was a robots.txt file disallowing all user agents in the image directory that another developer had added. This was causing the Apache installation to give a 500 error when attempting to access resources within the images sub-directory. If anyone has any further explanation I am willing to listen but for now this mystery is solved.
I may test this exact case in a stand alone Apache environment unrelated to OpenShift and attempt to reproduce this error. :) Happy Coding.
I'm getting the following error intermittently when making a call from my ASP.Net MVC web application which is using Dapper to query MySQL.
Unable to connect to any of the specified MySQL hosts.
The exception only occurs when my web app is published to Azure. It has worked 100% of the time when I run the code locally. I've deployed the code to a second azure website, and also get the exception there, again intermittently.
The MySQL database is running on an Azure VM (Ubuntu). This server also has some R scripts that access the database, which are being run at a set interval. I've had no connectivity issue with these either. It is just the .Net code that's struggling.
I've scoured the web, but don't feel like I've turned up anything of value. Most of the links have pointed to a connection string problem, but since it works intermittently that doesn't seem to fit my problem. Some links have referenced DNS issues, but I'm getting the same problem when I use the IP Address instead of the machine name for the DNS server.
I'm sure I need to track down more information, but I'm not sure where it would be. This is my first foray into using a MySQL db in this fashion, and I'm not familiar with config options or log files on that side of things. I feel similarly about Azure websites with database interactions too.
What can I try next?
Just to drive home the point about this error being intermittent, here's a screenshot from the Runscope job that's hitting the page (thus triggering the MySQL query) every 5 minutes:
I was able to fix (or perhaps "circumvent") this problem by adding the --skip-host-cache flag to our mysql configuration file. I still don't fully understand what the root of the problem is, but we haven't had any issues with MySQL connectivity from the Azure website since adding that.
I've got a Wordpress blog hosted on Linode under Cherokee web server, but the performance has been problematic the last weeks and I'd like to give a chance to Nginx.
So I've made a DB backup of the current site, setup a LEMP platform, installed wordpress, and the "new" wordpress, with no articles (yet) on it works as expected.
But when I restore the mysql database from the current blog, the site shows a blank page. I've copied all the wp-content directory onto the new WordPress directory, and I've tried to disable all the plugins, but nothing changes.
In fact, there's an even more important problem: I can't login with my old admin/pass account, that should be inherited from the old database. In fact when I do a SELECT on the wp_users table, everything seems to be fine (equal to the old installation), but I can't login no matter what I do.
I've even tried to change the admin password with an UPDATE and the MD5 function under mysql, and although the table is updated, the pass does not work either.
So all I get is a restore I can't access
The issue causing the blank page is likely that your old install used a theme other than the default, and since you haven't copied wp-content over, it's looking for a theme that doesn't exist. I find that with importing an installs database, this happens rather than it just reverting to a default theme, as it does when you delete the current theme on an active install.
Something you may consider trying to get around the login problems is doing a WordPress export (Tools -> Export). This will work if you don't have much media attached to your current posts, as it will only copy post contents, and not attachments. Import that export to a fresh WP install on your new platform and both problems should be solved.
Could be a plugin problem; rename your plugin folder to "oldplugins" and see what happens.
Reupload fresh copies of all WO core files/folders, except for wp-config.php and wp-content
Could be a permissions problem; check http://codex.wordpress.org/Changing_File_Permissions
And: did you change DB table prefixes?
I had this problem but eventually successfully restored it by trial and error.
The steps that worked were something like this:
uninstalled wordpress
installed a version that was working before the upgrade
activated same plugins (same version) that were installed before
restored the database
here's where it gets fuzzy, but had login problems and content would show but no theme, and admin login redirected to root site
did this procedure for changing site URL:
http://codex.wordpress.org/Changing_The_Site_URL
don't know why that was necessary but after a few minutes, the links started working. And after having to request a new admin login by email several times throughout the process, I was able to admin login again.