https://cloud.google.com/debugger/docs/setup/java
https://cloud.google.com/debugger/docs/setup/nodejs
On these pages it is mentioned that VERSION and MODULE are to be passed to the service while starting the Web Server. For the deployments done outside of GKE and App Engine, how to find the version?
The docs on the links above says
VERSION is the app version (e.g., the build ID). The GCP Console displays the running app as MODULE - VERSION. Examples: v1.0, build_147, or v20160520.
But not sure where to find it.
You can pick any names that makes sense to you for MODULE and VERSION. They will appear in as "MODULE - VERSION" in the app selector on the Debug page.
Related
I've played with Microsoft Bot Composer and have checked the extensibility points but it looks like it is not possible to deploy the bot to other clouds.
Please confirm my assumption.
My goal is to achieve deploying without additional development if possible.
Deploying a Composer bot is somewhat more complicated than deploying an ordinary Bot Framework bot because the Composer bot is not stored anywhere in a deployable state. Composer must bundle your specific Composer project files together with the centralized Composer runtime in order to create a deployable package.
However, Composer does come with a way to convert your Composer project into an ordinary bot project that can be deployed just like any web app. This is called exporting (or ejecting) the runtime. You can find out how to do that here.
To export your bot runtime:
Navigate to the Project Settings page of your Composer and find the Custom runtime section.
From the Custom runtime section, toggle Use custom runtime then select Get a new copy of the runtime code.
In the pop-up window select C# and select Okay. A copy of your bot's runtime will be added to the bot's project folder and can
be accessed in the following directory: C:\Users\UserName\Documents\Composer\bot\runtime.
I'm pretty new to the Google Cloud Platform. I have deployed a Python 3 Flask app in AppEngine Flexible Environment using the Google Cloud SDK and the app works fine. I just want to view the source files deployed, in the cloud. Is there any way to view my project files in GCP?
You can view the source files by clicking on tools > debug next to the app version on your versions page
Alternative, you can go to your instances page, click on SSH next to one of the instances and you will enter the debug mode for that specific instance.
This will open a console in your browser and you can start a shell in the container that is running your app, as described here.
PS: apparently this is possible only for the Flexible Environment
I am trying to create a web application using python on the google cloud platform. I have followed Google's quick-start guide and completed it.
App currently just prints out text
However, I am struggling to figure out a way to create a gui. I am aware of the python modules tk and tkinter and I have tried to use those with no success. I also saw the warning in the Google Cloud Console about how installed modules only exist for the current instance of the app - but even when installing the module directly before deploying the app - it still throws an import error.
I did some research and followed this guide: https://cloud.google.com/appengine/docs/standard/python/tools/using-libraries-python-27
Assuming I didn't miss any steps - would this guide solve my problem? Or is there a better way to create a GUI?
Any suggestions are encouraged. Thanks
App Engine is web oriented service. Read about it in the overview and the appropriate gui there would be a web based one.
If you want to have a remote server that will server graphical applications look closer at Google Cloud Compute Engine where you can have a VM instance, where you can install and run any application.
I have downloaded WSO2 appfacotry and ran it locally for testing purposes. It first gives carbon login and in the running application list I could see the /appmgt jaggery application is running. Then I tried to go to the url through the link provided in Action column in that application list. Initially I was routed to http://{some_ip_address}:9763/appmgt/ and then I was re routed to https://appfactory.example.com:9443/samlsso which gives me error. (because I don't have appfacotry.example.com domain.) How can I run appfactory without this faulty URL?
Here's documentation on installing App Factory: https://docs.wso2.com/display/AF201/Installing+On-Premise
Also, note that there is now a hosted version, which you can use in the cloud with no configuration required: http://wso2.com/cloud/app-cloud/
Other than the 3rd party tools mentioned above, you need App Factory, AS, API manager, Stratos Controller and ELB to have all App Factory features
I'm using PowerBuilder Classic 12.1 to deploy a .NET Web Services target to IIS 7 running on my local machine. I'd like to be able to debug it. The documentation from Sybase says I should be able to. But when I run the debugger it says "Attaching to ASP.NET worker" and "Time left: 20 seconds". It counts down to 0 and then I see "Failed attaching to ASP.NET worker process."
I'm running PowerBuilder as an administrator, so I don't think that's the problem.
Suggestions?
Open your your project object that you are using to deploy with. If you have multiple project objects, then right click on your target in the tree-view painter and click preferences to open a dialog that let's you choose which target object will be used for deployment. Choose the one that is set with DEBUG symbol on and set to debug build.
I have had good luck debugging PB Web Services both IIS hosted and self-hosted.
I also found this in the PowerBuilder help file for you:
Using the DEBUG symbol
If you used the DEBUG conditional compilation symbol in code for the nonvisual objects you deploy as a Web service and you want this code to run, you must make sure that the enable DEBUG symbol check box is selected before you deploy the project. If you plan to debug the assembly or Web service, you should make sure the project is deployed as a debug build.
** added additional details here on 1-26-13
This blog article will help you get WCF debugging to work in PowerBuilder.NET.
Testing & Debugging PowerBuilder.NET WCF Web Services