This may be a vague question but I have been unable to find any help/tutorials specific to my situation and am stuck.
I have built a website using Eclipse (Dynamic Web Project.) I then deployed this application using Tomcat and can see it by going to localhost, however, I am struggling on how to actually deploy it to the cloud.
I am trying to use Google App Engine but am open to other (free) alternatives for deploying my web application.
With Google App Engine, I registered for an account, made a new project, connected it to my github repository and confirmed the correct code is listed.
However, when navigating to project_id.appspot.com (mine is http://mapp-development.appspot.com) I get a 404 error.
I have attempted various deployments and even made an entirely new Google Web Application Project in Eclipse for testing which worked but weirdly deployed to http://1-dot-mapp-develop.appspot.com/ and is the test files which I do not know how to correctly modify.
Is there any way to upload/deploy my existing web application to Google App Engine (as a .war or otherwise)?
I am new to web development and apologize for any unclear specifications. Any help would be greatly appreciated!
Edit: I have also tried (in Eclipse) right clicking the project and choosing "Deploy to App Engine" under Google however it states "mapp-website is not an App Engine project".
Edit2: I had a stupid mistake, I confused my Project ID (mapp-development) and app id (mapp-develop). I am able to successfully make a new Google web project and deploy it to mapp-develop.appspot.com
Sorry for the trouble!
Here are three ways to deploy:
Make an App Engine project in Eclipse
Deploy via Git
Deploy via GitHub
It seems like you tried #1 with a project named 1-dot-mapp-develop. If you select deploy from Eclipse, a dialog box will pop up with a link to "App Engine Project Settings" where you can change the project name (to mapp-development and version).
Related
VSCode sees my Blazor server app as an Azure Function. Right-clicking on my publish folder I only have the option to Deploy to Function App, instead of Deploy to Web App which logically shows me only my function apps from azure. How is this determined by VSCode? I have checked the project file, but I do not see anything obvious wrong.
I tried Googling this, but the search terms only brings me to tutorials where this problem does not exist.
I was missing the Azure Web App extension. Once that was installed, the option appeared
The Google Actions SDK has been rewritten again for version 3 and comes with a completely new developer platform with different ways of working. As far as I can tell, there is no way to migrate a legacy (Actions SDK V2) action to the new SDK and Actions Console experience.
Is there a documented way to migrate to V3?
Is anyone who has successfully migrated able to share their experience and any problems they ran into?
I haven't found any usable documentation on switching versions so my best guess is to start from scratch with a new project, then delete the old one and rename the new one. Is that likely to work?
My app is a simple conversational Action implemented with the actions-on-google#v2.x SDK. I did not use Dialogflow at all.
Progress so far
I've had some partial success by using the new version of the gactions CLI.
I created a new project using the new web console experience then pulled the configuration down from the server. I then pulled my existing project configuration down, edited the files to match the test project, then pushed it back up.
This has resulted in the web console UX changing to match the new experience but there is a residual error that prevents me from testing my app.
Custom actions can only be specified in Conversational Actions projects.
This makes me think that there is some kind of project type in the back-end that determines what should happen in the web console. Pushing a modernised configuration up to the server seems to have changed the UI mode without changing the project type, causing an issue that prevents any maintenance on the old app or any migration to the new version of the system.
Update: A new migration workflow for Dialogflow Actions was just released. This is not relevant to my app because I never used Dialogflow.
new to ibm bluemix. Steps to be followed to develop a application on eclipse and to depoy using IBM Eclipse Tools for Bluemix and cloud foundry as well.
You could find all information you may need for your question in the Bluemix Documentation
https://console.ng.bluemix.net/docs/
On the following URL you could find a "Step by step" guide using Bluemix tool:
https://console.ng.bluemix.net/docs/manageapps/eclipsetools/eclipsetools.html
Instead on the following URL you could find a "Step by step" guide using CF push for a Java app on liberty runtime: https://console.ng.bluemix.net/docs/starters/liberty/index.html#liberty
First of all you can follow the instructions here for installing the IBM Eclipse Tools for Bluemix https://marketplace.eclipse.org/content/ibm-eclipse-tools-bluemix
Secondly, you can follow this tutorial to know how to push an application to Bluemix using the tooling. https://www.ibm.com/developerworks/community/blogs/941f1004-4e3d-4a4b-87ed-30d8045fde4e/resource/IBM%20Bluemix%20Tutorial%20-%20Connecting%20Eclipse%20to%20Bluemix%20v2.0_files/IBMBluemixTutorial-ConnectingEclipsetoBluemixv2.0.pdf?lang=en
There might be some UI differences in the IBM Eclipse Tools for Bluemix tools that you will install from the first link vs what is shown in the second link. These differences are however just cosmetic (like using terms IBM bluemix vs Cloud foundry while defining a server). Overall the functionality remains the same.
Also apart from the use-case described in the tutorial (second link), you can also create new projects (web projects) in eclipse and push them to Bluemix.
In order to test your projects locally, you would need to install local WAS liberty profile (in case of JavaEE projects) or local node js (in case of nodejs apps). You can do all the testing locally on the local servers and once you're confident about your development, you can push the projects to Bluemix.
Thanks,
Gaurav
Though this is a very old thread but this will be helpful for future references. One can setup the Bluemix server in an IDE like eclipse by straight forward adding a new server and can push the application directly. However a more user friendly approach is to deploy it from cf commandline. You can deploy the application independently or even package it with the local server. You even have the options to provide inputs like hostname in the commandline. Please go through the Bluemix docs for detailed specifications.
I am trying to create my first web app on Bluemix.
I created a Java Liberty Runtime and downloaded the Starter Code to
work on Eclipse.
I installed IBM Bluemix tools to Eclipse and
imported the starter code as an archive file.
When I try to run application on IBM Bluemix Server, it is recognizing the starter code as another new application and saying "There is a deployed application with the same name." So, I cannot update the application on eclipse and also there is two different applications are being seen on server view:
When I try to go application homepage it is giving:
Not Found
The application or context root for this request has not been found: /
Thanks for any comments.
The IBM Eclipse Tools for Bluemix recently added the ability to map and unmap a Bluemix app with a project in your workspace: https://developer.ibm.com/bluemix/2015/04/02/updates-ibm-eclipse-tools-bluemix/
To map a project, right click on an existing application in the Servers view and select Map to Project.
I was able to get this to work. I modified the manifest.yml file a bit to have a unique name and hostname. When you deploy this change the hostname and name to something unique.
applications:
- disk_quota: 1024M
host: e-urlabel-jbs
name: e-urlabel-jbs
path: webStarterApp.war
domain: mybluemix.net
instances: 1
memory: 512M
Note. I changed the domain as my account is in the US instance, but for yours to work change it to eu-gb.mybluemix.net.
I just realized that there is a recent update which provides ability to map and unmap Bluemix apps with projects in the workspace. It has come with the fresh version of the Eclipse Bluemix Tools. I solved the issue by mapping my Starter Code and Bluemix Project:
right click on an existing application in the Servers view
select Map to Project
Source: https://developer.ibm.com/bluemix/2015/04/02/updates-ibm-eclipse-tools-bluemix/
I have installed Eclipse Java EE Luna Release (4.4.0) and App Engine SDK 1.9.10
I have created a new Google - Web Application Project and selected the Generate Project Sample Code option. I changed nothing about the project.
The generated project successfully deploys and runs locally. However when I deploy this to AppSpot I get an error message "Remote Procedure Call - Failure" when clicking on the "Send" button on the sample form.
Are there other steps I need to perform in order for the generated project to be successfully deployed to AppSpot?
My goal is to have a starting application that deploys so I can start learning to use Objectify and GWT to build applications. If there is a better way to go about this please suggest it.
Kind regards
Sean
I think seem to remember that sample code for the GWT builds a RPC-based HelloWorld or greeting example. In the auto-generated sample interface you type a name, a RPC call is made to server side and you get "Hello"+yourName or similar as a callback.
Check this link:
http://www.gwtproject.org/doc/latest/tutorial/appengine.html
This is a more advanced app, StockWatcher, from the GWT tutorials which is also RPC based and adapted for the GAE. You could start here: http://www.gwtproject.org/doc/latest/tutorial/gettingstarted.html to build this app (is really easy) and follow to the link above to deploy StockWatcher on the GAE, or check directly the steps on the first link and try to deploy the GWT "Greetings" example.
If you have already tried this or you do and there's still a problem, please provide the full stack trace, or the code you think might be causing the problem, so we have a better insight of the problem.