Currently using the Aptana Studio 3 plugin for eclipse (3.4.2) and I'm unable to start my rails 4.0 project.
Error: Ruby program /xx/xx/xx/xx/HelloRails/script/rails does not exist.
It looks like Aptana is still looking for the rails executable in script, while it moved to bin in rails 4.0. Is there any workaround/fix available for this?
Create a folder script in the root of the app and place rails file from the bin folder to the script folder then it will work.
You might need to change the web-server options in the aptana setting also.
I was having the same problem but this fix fixed it
Related
I have a project which is done with Laravel 5.6. But My current server doesn't have php 7.1 installed yet. How is it possible to downgrade to Laravel 5.5?
I also down graded my project also, but then I was getting ton of errors. But most of them were about unfamiliar key words and unsupported packages. So, success depends on your project’s dependencies and also your effort.
Follow these steps.
Backup your project
Change the value of Laravel version inside the composer.json to Laravel 5.5
Delete vendor folder
Run composer install
** By then you will have to take care of any issues in your own code because there should be new functionalities in earlier versions which
is not used in older.
Or
Go to this page and do the instructions in reverse order
Private nuget server can't find packages after upgrade
I had to update the nuget server to get it to accept packages that were failing to upload (apparently the package format changed in dotnet core or something). Now all the previously uploaded packages aren't showing up in nuget. I can see all of them on the server just sitting there in their directories. But they can't be found. New packages are ending up in the server's package directory rather than their own directories.
From prior experience I don't think just copying the packages into the packages directory is going to work.
Trying to actually upgrade the NuGet.Server package from v2.8.6 to v3.0.2 appears to work but in the end the package is still at v2.8.6.
Don't try to upgrade nuget.server projects. That way lies madness.
Carry out the instructions like making a new one.
1) Create a new empty Web Project; target framework is NET Framework 4.6
2) Add NuGet.Server version 3.0.2
3) Fix duplicate <compilation> tag in web.config
4) Apply your API key to web.config and any other nuget configurations you have.
5) Remove old project from installation directory; leaving behind only the Packages directory and optionally any static files you uploaded to the installation directory itself (I keep a copy of nuget.exe and local project icons there).
6) Copy build output of new project to web installation directory.
It starts working. I don't know what's up with upgrading but it ends up with a smashed web.config and who knows what else.
I started working on this project on my home PC on Windows 10 using the latest version of Ionic CLI and Typescript and ionic serve works perfectly there.
However after cloning the exact same project to my work PC with Ubuntu which is also running the latest version of Ionic, I get this error when I try to use ionic serve:
"www" directory cannot be found. Please make sure the working directory is an Ionic project.
So obviously now on this PC it's not compiling the Typescript before running it. Somehow on my work PC it thinks this is a plain JS project?
I'm using Visual Studio 2015 community along with some other in our team. A mvc web application that I created works fine on my machine but when others get it to build, all packages download successfully but some of the core MVC such as Microsoft.AspNet.Mvc, Razor, etc don't install.
What was weird that on their machine, if they went into PM and downgraded the MVC package to 5.2.2 and then upgraded back to 5.2.3 it worked. But now when setting up the build on our build server, we get the same issue!
Any ideas why this bizarre behavior?
Didn't check that but why would that matter? When the Dev downgrades the version on 1 package and then upgrades back everything is as it should be
EDIT (4th Oct 2016) after investigating a bunch of things:
One of the developers at one point committed the "Packages" folder which sits at the root which had the "Microsoft.AspNet.Mvc" and other folders but without the dlls. This made the "Restore packages" not really "Restore" these as the folder already existed but when the build was run the artifacts weren't actually there in the folder to be moved into bin.
I deleted the packages folder, added it to gitignore and committed the change which made everything 'green'!
I have just downloaded cakephp latest version 2.3.0 and trying to create skeleton application
using bake command.
Problem is when I execute the command cake bake at /app>cake bake. Following message I am getting:
Welcome to CakePHP v1.3.2 Console
App : app
Path: /var/www/cake-acl/app
Your database configuration was not found. Take a moment to create one.
Database Configuration:
You can see, console is showing Cakephp version 1.3.2, even I have downloaded 2.3.0, thats why console is trying to create 1.3 version scripts for e.g. app/config folder instead app/Config (2.0 convention).
Why this is happening, Am I missing something?
If you were using v1.3.2 before downloading 2.3.0 version then it is possible that you might have set path for v.1.3.2 in your environment settings. So you need to change that to your latest version.