"BaconQrCode\Encoder\Encoder" not found - docker

I am using SimpleSoftwareIO/simple-qrcode in Laravel 8 application.
Provider is loaded successfully.
enter image description here
aliases is also added.
enter image description here
I am loading the QR code in the blade file which is working fine in the local development server.
When I load that in production which uses Nginx and Docker. I am getting the below error.
enter image description here
Can someone assist in this issue.
I have tried to downgrade the versions of the liabraries. But it is not working on the nginx production server.

Related

I can not open the url of the site deployed with dokku

Hello everybody) I started learning dokku. Going through the tutorial from the documentation for the Heroku Ruby on Rails "Getting Started" app I can't go to url generated by dokku in the browser. I am only using my local machine while learning and doing git push to localhost. This command works without errors, the container works, I get the url to the site, but I cannot open it in the browser. The same problem appears with another project, when I try to deploy a python django project, this is just a project skeleton created by django, without my code. It must show a welcome page and I want to see it when the site is running on dokku but I cannot go to the url. I tried to use dokku domains and dokku proxy but couldn't solve the problem. Please help me figure out how to fix this. I'm new to dokku, docker, nginx and deployment so the problem can be trivial. I'm also want to know on which ip, port dokku runs the sites and on which ip do I need to run the wsgi server inside the container?

Azure url encoding/decoding issue

I've recently moved a Rails 6 web application to Azure Web App service using Linux from an AWS Elastic beanstalk environment. I'm having an issue with a particular URL, when searching the following link:
www.website.com/link/asd%2Fasw
I get a 404 error. In my browser the link remains as www.website.com/link/asd%2Fasw, but in myWeb App service logs it decodes the URL to:
www.website.com/link/asd/asw
Hence why we get the 404 page error. I'm unsure of why this is happening. In our AWS environment the logs recorded the link as www.website.com/link/asd%2Fasw and everything was working as it should.
I have tried modifying the web.config file, but have been told that being a Linux environment this file is not supported (unsure of if this is correct).

How to set in meteor --mobile-server when using nginx

I have on digitalocean my meteor application running but when I try and test on my iphone the app I am not able to see the login screen.
I don't think it's version dependent and I therefore do not list them. I am happy to provide all the config files if this helps but want to make sure that I am not missing anything conceptually.
My setup is that on my digitalocean (not real URL: https://ABC123.com) server I run the meteor app and the app works fine at the URL. The meteor application has been deployed a while back and is a different release from what I am testing now locally. Source code is quite similar though and it never worked on the iphone. nginx is used to forward the URL domain to
proxy_pass http://127.0.0.1:3100;
Here is the issue now:
I run from my local mac:
meteor run ios-device --mobile-server https://ABC123.com
and run from xcode on the simulator or my iphone and get the attached screenshot. You can see that there is no login prompt which I believe is caused that I do not connect to the server on digitalocean.
It's a also surprising that with the command meteor runs on localhost:3000 as well. But it's probably not the issue.
The way it should look is the below which is taken from the web page:
Thanks already in advance for any responses.
This is resolved. Using Safari as a debugger I noticed that the connection to the server failed due to a non AC SSL certificate. So, after I fixed the SSL certificates it does connect now.

Rails google drive gem issue with heroku

I have accessed my google sheet file using google drive gem with command
GoogleDrive.saved_session("./config.json")
Config file contains credentials to connect to drive. On my local machine server asks to paste as url in browser and paste authentication key.
I have done all this and on my localhost code is working fine.
But I have deployed my code to heroku and I am facing the issue. App crashes with logs saying to to find authentication code from given url and paste it.
I find this authentication code successfully but on heroku how to paste it? On localhost I was able to put in the key in terminal. How to make it run on heroku.
Please help me.

Getting 502 bad request after deploying Play 2.1.0 app to Cloudbees

I tried to deploy a Play app to Cloudbees (only via push to git repo from which it is built by jenkins), it compiled and should work but I get a "502 Bad Gateway" error when loading the app. There is no error shown in the console only that it answers "502 Bad Gateway" when trying to access it. But that's what I see in the browser, too.
Cloudbees say that there is no other manipulation necessary, just cloning/pulling the ClickStart-Project, making it you application and pushing it back. The Play project works fine locally.
I am very grateful for any help. Please let me know if I need to provide any other information. Thanks a lot!
Edit: It works fine with Heroku only adding a Procfile. I don't get the problem with Cloudbees...
In this case the error is due to the database needing evolutions to be run before it can start:
[warn] play - Run with -DapplyEvolutions.default=true and -DapplyDownEvolutions.default=true if you want to run them automatically (be careful)
Oops, cannot start the server.
#6eg39l651: Database 'default' needs evolution!
You can see the error in your application console:
https://run.cloudbees.com/a/strehlst#app-manage/logs:strehlst/odzh
or via bees app:tail if you have the bees CLI installed.
You can also deploy direct from your desktop if you like:
play dist
bees app:deploy -t play2 dist/yourapp.zip
And it will push direct to your app (if you don't want a continuous deployment pipeline).

Resources