Im trying to deploy a PERN app to AWS ElasticBeanstalk/Code Pipeline but having issues. Im pretty lost in what the problem is as the causes are broad. Im not sure if my package.json is not configured correctly or what I need to do to move forward.
Any help would be great!
Error Log
Error Log
I'm building an API with Google Cloud functions and I had the same issue as the guy from this post: Could not load the default credentials? (Node.js Google Compute Engine tutorial)
When trying to use my API, I received this error:
Could not load the default credentials. Browse to https://developers.google.com/accounts/docs/application-default-credentials for more information.
So I went on and followed the steps suggested in the question I mentioned. I downloaded the gcloud SDK, installed it, and at the end of the installation wizard there is an option to run the google cloud cli immediately.
I ran it successfully and logged in properly, now any time I open the command prompt I can use the gcloud command without a problem.
Mi issue is the following. I'm running my commands in VSCode bash terminal and I get an error saying that the gcloud command is not found.
My project is in my D: drive, and the SDK is on C:, which I believe is the reason why the gcloud command is not recognized when I attempt to use it.
Should/can I install the Google Cloud SDK in my D: drive and use it there, or should I move my project to the C: drive?
I read somewhere that this might be a problem with the bash terminal, but I tried running it from command prompt in VSCode and I get the same error, so I guess it's got nothing to do with it.
Thank you for your time.
I am developing a GAS app.
Im using clasp to develop locally. I managed to get the connection working in order to run functions locally.
This required to move the GAS project from the default one to a new dedicated project.
I had to set up a proper OAuth ID in order to get the credentials for clasp, as they show in their Documentation.
The issue now is that the previosuly working webb app deployment dont work anymore. I get the next error:
404:
The requested URL /scripts/<MyProjectId>:run was not found on this server.
error screenshot
I'm thinking the web app deployment needs a proper OAuth or some other configuration in the new GCProject, but i cant figure out what it is.
Thanks in advance for any help.
I’m getting a weird error when trying to deploy my Vapor project onto GCP App Engine. I was able to deploy it previously but this error just began out of nowhere. I believe it has something to do with my Fluent Migrations but don’t seem to know how to pinpoint this issue… does anyone have any idea as to why my migration might suddenly fail when it worked before? I followed this tutorial to get it up on App Engine: https://medium.com/swift2go/serverless-google-app-engine-flex-docker-runtime-cloud-sql-backend-with-swift-vapor-web-alfian-c8310acfea0d
I already looked at this stackOverflow question but it is not the same as my issue: Google App Engine Deploy Error Code 9
Sounds fairly simple but I've been trying to do this for several days now and have hit a brick wall. Below I've listed my attempts so far, in all cases it works flawlessly when running locally, but falls over as soon as I deploy to Azure. Note that I am using an Azure website rather than a VM ( mainly because of cost implications - I'm aware that using a VM would most likely solve the problem ). The only way I've found to make this work is to use a sqlite database deployed within the project.
Things I've Tried:
1) Create a MySQL database using the azure partner clearDB. 'manage.py syncdb' works fine, can run up and use the site locally using 'manage.py runserver'. Deploy to azure and it fails with an unresolved import for Python-MySqlDb.
2) Create a SQLAzure database and use django-pyodbc-azure to connect from django. Again, syncdb / runserver work fine locally, deployed to Azure gives unresolved import for the dbapi module.
3) Use sqllite3 as db engine - works fine in both cases, but no redundancy and ( seemingly ) slow data access.
Looking at the tutorials for deploying a Django app on Azure Websites, none of them go into any detail about databases, just stopping at the point of creating a Hello World! page. I refer to: this and this
The website we're trying to deploy is running on a reserved instance. I've tried all of this with both Django 1.4 and 1.5. I'm using virtualenv / pip to make sure all dependencies are included in the site-packages I'm deploying, all of which is included in the git repository. Have also gone in via FTP to verify that all the required files are being uploaded.
SURELY - there must be a way to set this up correctly? If not, having Django as a feature of azure websites seems entirely pointless.
Any help greatly appreciated!
EDIT
Traceback from Azure error logging for the clearDB solution:
File "D:\home\site\wwwroot\site-packages\django\utils\importlib.py", line 35, in import_module
__import__(name)
File "D:\home\site\wwwroot\site-packages\django\db\backends\mysql\base.py", line 17, in <module>
raise ImproperlyConfigured("Error loading MySQLdb module: %s" % e)
ImproperlyConfigured: Error loading MySQLdb module: No module named MySQLdb
ErrorCode Access is denied.
(0x5)
I have Django and MySQL working on Azure. The MySQLdb module contains more than just the MySQLdb directory. It also contains 4 platform-specific files beginning with _mysql.... Make sure you include those files when you push to Azure. If you don't your Django project will work locally but not remotely. You don't need to use a pure-Python MySQL adapter.
Here's a walkthrough: How to host your Django apps on Azure for free.
Solved - kind of:
Using a pure python mysql driver works ( as I kind of guessed it might, this being caused by an environment limitation of azure )
For future reference - this project sorted it all out for me:
https://github.com/jloic/django-mysql-pymysql
note: Azure seems not to pick up python eggs in site-packages, so I had to extract the contents into site-packages and tadaa it all worked.
Next step is to try using the cython version, although the speed of the site seems fine so far.