I am trying to connect my Node.JS + Wit.AI project built with PhpStorm 2016 to Heroku, but all the information that I find on how to do that seems to be either quite outdated or doesn't match my IDE at all...
Anyone had any success connecting Heroku to PhpStorm 2016 somehow?
So far, I tried these plugins which didn't work:
https://plugins.jetbrains.com/plugin/6659
https://plugins.jetbrains.com/plugin/7605
On the IntelliJ IDEA page ( https://www.jetbrains.com/help/idea/2016.2/getting-started-with-heroku.html ) it says to go in Build, Execution, Deployment | Clouds, but while I can see Build, Execution, Deployment in my settings, there is nothing close to a "Clouds" option...
As far as I'm aware full Clouds support available in IntelliJ IDEA only .. although some services are available in certain IDEs as well (e.g. Heroku is available in RubyMine).
As for PhpStorm/WebStorm -- https://youtrack.jetbrains.com/issue/WEB-15174 -- watch this ticket (star/comment/vote) to get notified on any progress.
Related
After recently updating my project to meteor 1.2 and including the new ecmascript package (to use ES2015 features), I realized that my server debug breakpoints will never run, no matter what I do.
After reading about different ES6 posts on meteor forums and jetbrains , I tried setting up file watchers to create sourcemaps, but:
meteor complains about the generated files(so you have to move them to special folders in order to keep going)
It still doesn't work :(
Setting up spy-js also didn't work (never tried before so maybe I did it wrong)
I could reproduce the problem with the basic TODOs application and debugging with default options.
It is fixed for now in EAP 11 builds.
Known issue, please follow WEB-18074 for updates. Unfortunately I can't offer any workarounds:(
I am trying to install jBilling community edition on heroku and/or appfog. I could not find any information on google on how to do this. I used the simple way to deploy the war file on heroku and that did not work. I am assuming there must be some configuration changes needed.
Before I venture into this I wanted to get a shout out and see if anyone has already done this successfully and has notes that s/he is willing to share with me.
jBilling has both installation guides (for windows and for mac/linux) and a Getting Started Guide on their website that list each step and walk you through the process. Try starting with those.
I'm involved in developing a sandboxed Microsoft Dynamics CRM 2011 Online plugin and have a set of tests that I can drive from a xUnit front end on my local machine given that I right-click the Package and select the Deploy option (and resort to using the plugin loader sample when that doesn't work).
I'd like to be able to automate the running of my tests on my CI rig, where I'll need it to upload a fresh binary as part of each run.
We've looked at http://pluginregcrm2011.codeplex.com/ but it has bugs that prevent it working for Online and in short looks like it's no longer being maintained and I'm not keen to take ownership of what should be a fundamental tool that a platform/ecosystem should just have.
Is anyone using that tool or another plugin uploader non-interactively? Am I missing something?
I know I'm late with my answer and I`m pretty sure that you already have found a solution which is working for you.
However I felt the same pain and I have hacked a small application which could be used to simply update the plugin assembly, without doing any configuration work.
PluginAssemblyLoader -f "C:\MyPlugin.dll" -c "Url=http://crmserver/org;"
Please see http://msdyncrm-contrib.github.io/PluginAssemblyLoader
There isn't an easy OOB experience with this but the CRM 2011 Developer Toolkit just uses a set of MSBuild targets that you can call yourself. It's just MSBuild, so you could hook it into your CI build if required. If you install or just extract the Developer Toolkit MSI in the SDK you'll find the following two files in there...
Microsoft.CrmdeveloperTools.CrmClient.dll
Microsoft.CrmdeveloperTools.CrmClient.targets
As an aside it would be nice if MS would open source this as the current implementation uses predominantly sealed and internal classes within the custom tasks.
This question is more of type "has anyone experienced something similar before and if so, what was the issue?".
At work I use an iMac to do my daily programming. After some initial (and still occasional) struggles, I got my project running on Virgo server. Stand-alone or from Eclipse, both work.
I checked out the same code at home on my Windows PC, installed same version of Eclipse and Virgo. I took the same installation & configuration steps like on the Mac at work. I can get the project up & running stand-alone. However, when I try to get the project deployed from withing Eclipse, no matter what I try, some bundles would not deploy.
As one of desperate last options I even moved Virgo to a c:\v, just in case the path was to long. Still no success.
Did anyone experience something like this before? What was the reason? Any hidden configuration I might be missing?
Thanks,
Jan
you can have a look at the Virgo\work\org.eclipse.virgo.kernel.deployer_<someVersion>\staging\global\bundle\ directory. Virgo tooling should normally deploy to this directory and invoke the deployer. maybe there are some issues. i suppose, you already checked the debug-output-logs? maybe it issnt a problem of deployment but something else.
I am unable to compile my app in Monotouch when I select the full enterprise distribution profile I have setup. All the other profiles work ok.
To be specific: when I hit the build button I get
Detecting signing identity...
0 errors 0 warnings, just Build failed. Array index out of range
I am guessing this is a provisioning issue and I have failed to do something important.
There are pointers on the web to adhoc ditribution builds but no real documentation on full enterprise distribution.
I have the following:
Monotouch : Enterprise edition
Apple : Enterprise membership, have installed the corp certificate & dev user certificate and downloaded the provisioning certificates for dev, adhoc & enterprise and finally created the App ID.
I have spent 2 days scouring the web for similar problems but have found nothing really close. At one point I scrubbed all my profiles with Apple Dev site and re imported them and this resolved some other issues I was having.
Having the full enterprise rights/certificate means I do not need UDIDs, I just have to sign my life away to prevent illegal ditribution. The only thing other than just plain missing something on the provisioning front is that the UDID's are held in an array in the certificates and as I have none specified for this build it errors out. (But it shouldn't surely!)
If I use the adhoc distribution which as UDID's specified in it I can load it on my machine.
Any pointers would be greatly received
I had a similar situation.
"mtouch failed to build". No other messages.
Had to go through tech support and eventually found it was a compiler bug and they sent me a patch for my particular case. I assume it will come out in the next release.
However, I did learn two things along the way that may help you.
a) in my case the problem went away if I changed the "Linker Behavior" setting for the project. Project-> [project] Options -> Build -> iPhone Build -> Linker Behavior
Try all available options. See if makes a difference.
b) On the same iPhone Build options page you can enter "-v -v -v" to the "extra arguments setting. Now check the build output after compiling. There may be additional details.
Finally, I pulled my hair out for a few days with an error similar to yours. In the end it was a compiler bug. Novell was quite quick to identify and fix the bug. Maybe just log it with them and see what happens.
Good luck
I had this problem when switching between my "test" and "release" builds, which had different app identifiers -- I'd switched to the "release" provisioning profile, but I forgot to fix the app display name and app identifier under Build / iPhone Application. Doubt the display name makes a difference but the app identifier certainly does.