We have developed and deployed a Jekyll site and portfolio and deployed it to Heroku.
For some strange reason, the site at http://blueverve.com and the site at http://www.blueverve.com are out of sync.
Has anyone come across something like this before?
Thanks!
It looks like your DNS records have been setup incorrectly with your registrar.
For http://blueverve.com/ I see these nameservers:
ns-1082.awsdns-07.org.
ns-1961.awsdns-53.co.uk.
ns-337.awsdns-42.com.
ns-753.awsdns-30.net.
For http://www.blueverve.com/ I only see this:
ns-927.amazon.com.
Related
I am a student and have created my first Laravel App (A blog app). I have a layout/master view created named app.blade.php in resources/views/layouts folder.
I am using laravel 5.6.
It works perfectly on localhost but not on heroku hosting.
Here is my project structure
Here is my code in home.blade.php
Heroku hosting error screen below
Localhost view
clueless about this problem. I need your support.
EDIT
I solved the problem. I am on a windows system while hosting on a linux platform. So my sweet innocent windows was not updating the "Layouts" on server with "layouts".
But I am with another problem
Regards,
Arpan
but loading /login /register correctly
Now this doesn't end here,
when I type /login with the url it gives me
Now I observe that when i click the link it shows me Not secure connection and displays properly but when typing there is https but not displayed correctly.
Please help me analyse and figure out the issue.
Github repo link : https://github.com/ArpanKIIT2017/blog4b/
Its because the app was unable to find the file. But everything looks good. can you check if the file exists on remote server.
what are you using to push the files to remote server?.
try running
php artisan view:clear
on both local and heroku
Actually Heroku doesn't support SSL in free tier. So https actually won't work.
Finnaly migrated my app to postgre sql.
Problem mainly was due to the uppercase and lowercase representation of "Layouts".
So my app is Up and Running only with one problem that is heroku doesn't support file uploads. It is not storing any file upload. Searching solution for that but not related to this post.
Thank You
I'm having some major issues deploying a website I have built in Laravel which is a technology I am still learning.
I built the site on a temporary subdomain (new.example.com) on a brand new server. I have now come to deploy it so I removed the subdomain mapping in cPanel and changed the primary domain's document root to point Laravel's /public folder as described here.
This shows what I have done:
new.example.com - /public_html/mainsite/public
www.example.com - /public_html/mainsite/public
Now when I try to access www.example.com I get the error message:
No input file specified.
I saw this question but it doesn't seem to match what I have in my .htaccess file. I appear to have run out of talent to be able to fix this problem on my own and need help.
My questions are:
How can I resolve the error mentioned above?
Is there a better way to deploy Laravel sites to cPanel environments?
Have I created an XY problem for myself and I should be looking at something else to get this to work?
I wonder whether there's an easy way to add Basic HTTP Authentication to a Middleman deployed website? I found some Heroku specific gists, but nothing else.
The Heroku specific gists all seem to need a config.ru file, but do Middleman projects even have such a file? Mine don't.
config.ru is not specific to Middleman or Heroku, but is a convention for serving a rack-based app (see https://devcenter.heroku.com/articles/rack). If you want to have basic auth on a static site that you have built using middleman and then deployed, you will need to set it up in a way that's appropriate to that hosting. Where are you hosting the site?
I am using laravel forge and it's awesome. However i ran into one problem.
I created a server on digital ocean and referred my domains to that ip. Everything good and well so far.
Than i created a site. Used the deployer and yup everything worked like a charm, however now i added a second site to the server. and well yes it added the site. so /home/forge/website2.com. However now when going to my previous site: website1.com it shows me website2.com.. i rebooted the server, reloaded nginx nothing seems to work als in sites_available the paths look good.
Any idea's?
Are site 1 and site 2 on different domains, or are they just different sub domains?
Have you tried comparing the Nginx configuration (you can get to it from the Forge site) between the two websites?
To me it seems that your Nginx configuration is wrong. Lastly, are either of them stored on the "default" site on forge or did you qualify a url and keep "default" empty?
This issue has been resolved by taylor, He updated forge and this isn't a problem anymore.
I'm using CloudFlare in my website and it works perfectly. Problem is, I decided to host my static files like JavaScript, CSS, etc. in static.example.com and I don't know how to set up the subdomain.
I already tried adding a CNAME record (static is an alias of example.com) and it didn't work, and as a A record (static points to IPAddress) where IPAddress is the IP address that both www and example.com use.
I'm I doing something wrong? I've waited about an hour for any DNS propagation problems and still doesn't work.
If you have added the subdomain in your CloudFlare DNS settings (settings->DNS settings), then it should start propagating out after a few minutes or so. If you're still having issues with the subdomain, please contact CloudFlare with the domain name so we can look at it.
I had the same issue until I realized I had to click on the greyed out cloud on that row to activate Cloudflare on the subdomain. This is what it currently looks like:
The instructions at the top of the page clearly say you have to do this, but I'm not one of those read the manual types for simple tasks. I guess what would have really got the point across was some sort of notice the very first time I added a subdomain on my account.
Once you've clicked the icon, then the activated proxy will be indicated like this:
Oh well, hope this helps somebody else.