I have a mern app that I am using to fetch packages from my backend.
It works in development but not in production when I host it on AWS EC2.
I figured out that the reason it's not working id because I am getting incomplete response back in production. How is it even possible? I am frustrated right now.
Attaching some images and console logs in development and production.
The field packageImages is missing in production response!
Because of this I am getting error about trying to read properties of undefined.
Please someone guide me with this.
Related
We have a Cloud Service that we have been deploying/updating without issue. In the past two weeks every time we try to deploy the package we are getting the error "Deployment could not be created - There was an error processing your request. Try again in a few moments".
I am at a loss as to how to even debug the issue to get more detail. if anybody has any advice on how to get a better error description would be appreciated.
The only changes in this deployment are some changes to the static files in the package so it is unclear what is causing the issue. The process we use is (1) build the package, (2) upload the package, (3) deploy in the staging environment. The package gets uploaded but fails to deploy (step 3).
Any help as to what the issue is or how to get better diagnostic information woudl be great.
I'm trying to learn to deploy Shiny dashboards on Amazon's EC2 servers. I managed to find a good tutorial which I followed to the very end. Every step along the way worked except when I try to access the dashboard through my browser. I'll paste a few screenshots that may help you find where I'm messing up.
And this ( ec2-18-212-81-78.compute-1.amazonaws.com:3838/shinytest ) is the link that should lead me to the dashboard, but I get a "This site can't be reached" error, as if the site was offline.
Any help will be appreciated!
When uploading the wasm binary, as a compiled smart contract on the 'ink-workshop' - the canvas-ui that I am running just errors.
Canvas-ui error:
Uncaught error. Something went wrong with the query and rendering of this component.
Cannot read properties of undefined (reading 'args')
Step: 'Drag the flipper.contract file that contains the bundled wasm blob....'
The Github issues section associated is read-only, hence why I am posting here. Anyone know what might be the problem here?
Incase others are wondering what to do in this instance. I was able to deploy using the official polkadot web interface.
Connect your local running node via settings and there you can deploy your flipper contract.
This is a good article on the astar network docs on how to do it, using the basic flipper contract example.
There is a maintenance problem and they wanna fix it.
https://github.com/paritytech/canvas-ui/issues/119#issuecomment-1020114242
I wasn't able to find solid information on this and I wanted to ask developers who use Parse Dashboard:
What are the pros/cons of Parse Dashboard local installation vs deployment?
I currently run the Parse Dashboard on local installation, but I know that deployment to Heroku is also an option (my app is deployed on Heroku). I wanted to gather some information before deploying/not deploying.
Thank you!
I also have it running locally and I think for security reasons it's best to do so. If you setup the dashboard on the same server on which Parse is running, then you will have to take security measure to protect access to the dashboard and the config file which includes your masterkey and all that. This definitely outweighs the arguments to host it locally, which in my opinion only is that it's easier to access the dashboard.
If you really want to setup a dashboard on a server at least do it on a separate server.
I've migrated my parse app on a IBM Bluemix hosting using this node js app https://github.com/ukmadlz/parse-on-bluemix
Despite the parse server is now installed only on my hosting environment I'm trying to remove the very annoying limit of 30 requests per sec.
Does anybody know how to that? I've tried looking into parse server source code but I couldn't spot it..
Thanks
It's was already removed in parse server open source.