Another question regarding design automation.
I am trying to deploy the app to AWS but it seems that the appsettings.json file is not coming throug and the result is that I receive an error saying that the cliendid parameter is null.
Can someone help me through this?
I don't know why appsettings.json didn't made it to your AWS but if you use Forge Design Automation SDK (https://github.com/Autodesk-Forge/forge-api-dotnet-design.automation), there is way how to setup ClientID and ClientSecret using environment variables.
Forge__ClientId=<your client id>
Forge__ClientSecret=<your client secret>
Related
I want to ask about the Deployment of Forge API by Azure.
I had done it through the resource from Learn Forge, and it seems to work smoothly on the local site, but when I try to publish it, Although it shows permission
after I sign in, it shows 400 error refused, how can I do this for this error?
This is typically caused by an incorrect callback URL for the 3-legged authentication workflow.
When you develop your application locally, you typically set the callback URL (both in your application's code and in https://forge.autodesk.com/myapps) to something like http://localhost:3000/api/forge/callback/oauth).
However, when you deploy your application to Azure, AWS, Heroku, or any other cloud hosting provider, the callback URL must be updated accordingly. For example, if you deploy your application as an Azure Web App, the callback URL could look something like https://my-cool-app.azurewebsites.net/api/forge/callback/oauth. And again, you'll have to change the URL both in https://forge.autodesk.com/myapps, and in your Azure Web App settings.
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 am currently working on a project that uses Angular as frontend framework, Flask as backend framework and MySQL as database.
Furthermore, the developement of the application is completed and the source code is stored in private Github repo.
My next step is to deploy this project on heroku server. After done some research l found that i have to change the database to Clear DB which is the database available in heroku. As a newbie this is my first web app deployment to heroku server.
Is there any online source where i can refer that can fullfiill my requirement or if somebody has done this approach previousely could please list down the steps so i can follow them. Your help will be highly appreciated.
Thanks and best regards.
I had done a project related to angular and flask. I faced the same issue when it comes to app deployment phase.
I deployed the angular app and the flask app in two separate heroku servers. Using this method it is easy for you to do the furthure developments of the application as well.
Following are some reliable sources you can refer,
Deploy flask app to heroku
https://stackabuse.com/deploying-a-flask-application-to-heroku/
Deploy angular app to heroku
https://www.javaguides.net/2020/11/how-to-deploy-angular-application-to-heroku.html?m=1
After deploy both these frameworks separately you can replace your angular api call from https://localhost:5000/api/ to https://yourbackendserver.herokuapp.com/api/
We have an app, that works without problems on dev machine and deployed in cloud, but we are having problems setting it up on server in corporate network, where everything (e.g. views with information from database) except Forge Viewer and Forge API (e.g. upload) works.
It fails with a message "Underlying connection closed" when we are trying to get Autodesk Forge 2 legged token. We are using Autodesk Forge .Net SDK v 1.0.2.
We did additional tests and seems like all outbound API calls on the server are failing. I know there is not enough information to actually solve the problem, but I would appreciate ideas where to look for the solution.
I have grouped family of services as a Carbon Application and then deploying the same on WSO2 ESB. If one of those services fails during deployment then none of the other services are deployed on ESB, instead i get an Service laready exists exception upon retry.
It will be of great help if you could help me.
EDIT
I am using WSO2 3.0.1.
Make sure you donot have any traces of CAR file that you uploaded in the following paths.
1) <ESB_HOME>--> tmp--> carbonappuploads
2) <ESB_HOME>--> repository-->deployment-->server-->carbonapps
3) <ESB_HOME>--> carbonapps.
After deleting any traces of carbonapps in the above mentioned apps, Restart the ESB server. Then try to upload CAR file again. Hope this will work.Thanks.
According to your description I guess that you are trying to deploy a Carbon Application aRchive (CAR) file which contains a set of services in WSO2 ESB. First of all I would like to suggest to use WSO2 Application Server [1] to deploy services instead of the ESB.
Regarding the error you get during the deployment I guess you may have defined two services with the same name or you may have already deployed this CAR file before. Hope this will help. If this is not the case please provide more information about your problem so that we could try to identify the problem.
[1] http://docs.wso2.org/display/DVS320/Creating+JAX-WS+and+JAX-RS+Service+Projects
Thanks