My organization is currently trying to move away from Heroku and we just migrated our React.js app to Nextjs. Originally I had considered going with AWS but Vercel seems to have a lot of benefits that would help us in the long term.
Currently our Laravel backend is still hosted in Heroku with a Postgres database. When I try to deploy, it appears that I cannot make a GET call.
This Next.js code works as expected on a Heroku dyno, but not when I attempt to deploy to Vercel.
Are there any gotchas, or considerations I should be aware of? Has anyone else ran into this issue?
Figured out what it was. Hope this helps somebody else! We had the .next build in our .gitignore folder because we had to switch back and forth between a legacy project and the .next folder caused some big issues. We just removed it and everything is building as expected. Still curious as to why it worked in Heroku and not Vercel though.
Related
I have question about Shopify app development and the deployment process.
I've used the getting started guide here, and I have an app that works fine when I use npm run dev and view the app in the store admin.
However, of course, once I stop the server from running, the app is no longer accessible.
I believe I need to deploy the app to Heroku (or something similar) in order to have it work in a non-development environment.
It doesn't seem like there is much guidance online from Shopify about the best way to go about this.
Does anyone know what steps I need to take in order to deploy my app to Heroku, so that I can use the app in by test store on another device?
It seems like every guide online stops JUST BEFORE explaining this process and I can't figure out why! I have tried everything online but nothing has worked:
Adding the code to Github and connecting it to Heroku
Using Docker
Any help is appreciated. Thank you!
You have zero obligations to use Heroku. If you have an IP address dedicated to your house, you could host the App using your house. If you co-locate your own server at an Internet business, and they give you IP addresses you can use that. If you wanted to use Amazon directly, you could use EC2. If you wanted to use Linode, or Azure, or any other cloud service, feel free! It is up to you!
Using Heroku (built on AWS) is traditional only in the sense that it is the original easy peasy hosting in the cloud service. Play with Heroku by reading Heroku-specific documentation or hosting information. This has nothing to do with Shopify. Shopify only mentions Heroku because traditionally, developers used it. No other reason.
If you want to learn how to use Heroku, 100% there are blog posts within easy reach for you to study and learn from.
I made a Reaction Role Bot (Discord.py) a week ago, and when I'm hosting the Bot on my own PC everything is working perfectly fine. But when I#m pushing the File in Heroku and try to run it there, there are many Errors like this: https://gyazo.com/d40c7051aa7037a31101d51443314c90
I really don't know why there is an Error, because i changed absolutely nothing on the File.
Is there someone who maybe know why this happens and how i can get rid of this error?
It is likely Heroku pulled discord.py 1.5, and you are running an older version on your local machine. v1.5 introduced support for gateway intents, see this page on how to update your bot code to work with them.
Last night after I pushed my latest release to the heroku git master branch the site was available via the https://appname.herokuapp.com address. This morning when I made one small change to a CSS file and pushed it again I discovered that the site is not available over https but is available over http (and everything looks right). I can't believe that a simple change to a static file could cause this. Has anyone else had this problem? I'm using the free account (planning to upgrade to hobby soon) so I can't get Heroku support. Is this just a temporary outage on their part or do I need to fix something? Thanks!
OK, this turned out to be a local issue with the computer I was using that cleared up as suddenly as it had appeared. Thanks for the comments and I now have logging to boot!
So...i'm pretty new in hosting websites and horst yet with hosting in cloud services. I'm having a pretty bad time trying to host a Laravel 5.7 application in AWS and i really need some help/direction.
My situation is like this:
I have a normal Laravel 5.7 app that uses MySQL database and Laravel Queue(database type).
I need a process to constantly listen/monitor the job queue and execute them.
The thing is, i just lerned that you can't use normal hosting to do this(listen the job queue) and that i need a VPS service.
In my searches i saw that AWS have a 1 year free trial and i thought it was worth to take a look. The thing is, i started from EC2 and got as far as installing apache, mysql, php, git, etc. I made a clone of my project to the /etc/www/html and install composer dependencies... but i'm not quite understaing what to do for the app run, and in looking for tutorials everything is always differet and nothing ever works. I dont know what else to do, this is my first contact with cloud services.
That said, my question is what can i do to host my Laravel 5.7 app in amazon, and is it really the better solution for my problem ?
I am currently doing what you're trying to do. The configuration is outlined here. You will need to install supervisord. You didn't leave enough information about what type of instance you're running, so I can't get you more complete instructions, but if you follow these steps, your queue should run as expected.
This help site (http://www.howtoinstallghost.com/how-to-install-ghost-on-heroku/) says that "Heroku should not be used for production!". What could the possible reasons for them saying this be?
I just want to set up a simple blog.
Thank you in advance.
From the same page;
Why do you only recommend Heroku for testing?
If you upload any images to your Ghost blog hosted on Heroku they will eventually be lost because of the ephemeral filesystem. There is no warning about this so we do not currently recommend anybody to use Heroku.
In other words, since any files you write to the file system at Heroku may go away at any time (and is not shared between instances of the blog if you try to scale out), you may lose all uploaded pictures at any time (once a month/once a minute, who knows) and need to upload them again.