I am new to rasa, i have watched some old training videos on youtube and other sources. There they have told to install rasa_nlu and rasa_core.
But when i check on rasa website, it says just to install "rasa" not but "rasa_nlu" and "rasa_core". I am assuming rasa_core and rasa_nlu are deprecated. So just installing rasa will work right?
No need to install rasa_core and rasa_nlu separately?
Correct, just installing rasa will work.
You no longer need to install these parts separately: rasa core and nlu were merged in 2019 (see announcement here).
Related
I have been trying to add newrelic support for the better half of the day now. (isn't this supposed to be easy?) Thinking I might be running into issues because of forge? I know Forge used to have the ability to plug in a key and your off to the races. I no longer see that option?... Did they remove support of NewRelic?
I keep getting the following issue when even trying to install manually using New Relics instructions:
sudo apt-get install newrelic-php5
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package newrelic-php5
Using Laravel Forge, Lumen, Amazon AWS, HHVM and None (2 instances running)
Thanks
Citti
Even if you could make the installation work, unfortunately New Relic doesn't support HHVM nor they are planning to.
According to Laravel's documentation, it says "This method of installation (Laravel Installer) is much faster than installing via Composer".
My question is why & how it is much faster than Composer?
As you can see from here https://github.com/laravel/installer/blob/master/src/NewCommand.php#L97
it actually downloads a latest zip which is cached to serve faster
that's why it's fast. Also when you download you will see all the
packages are installed. So no package are individually installed
that's why it's more faster.
You can checkout more about the package source code https://github.com/laravel/installer
A couple of years of go i used to program using PHP, but without frameworks. With these recent developments I've decided to get in the to the game and try using one. I've decided to use yii 2.0 .
I've read some of the documentation and in my opinion there is some lack of information (at least for who is getting started), so i´m having some problems installing yii 2.0 on my computer using Xampp. The PHP version is 5.5.9.
From what i could understand i downloaded the yii 2.0 framework, extracted the content and copied to c:\xampp\htdocs\yii2
I've already installed the composer, so the the next thing to do i think would be, using the cmd, do these two lines of code:
composer global require "fxp/composer-asset-plugin:1.0.0"
composer create-project --prefer-dist --stability=dev yiisoft/yii2-app-basic basic
The problem is when i do the last one it asks for username and password i think of GitHub. Can you tell me if I'm obligated to have an account on github to install yii 2.0 framework.
Is there a way to get around this?
Yii2 is integrated with composer asset plugin. It allows download Bower and NodeJs packages through Composer.
Github account is required to overcome API rate limit. Here is the explanation from the main contributor of this extension:
It's a rate limit of Github API. In anonymous access, Github at a
greatly reduced limit (60/hr it seems to me), and we must be logged
with a token for have a much higher limit.
See composer/composer#1569 and composer/composer#1877
The problem also exists using Nodejs and Bower.
You can find it in this issue, it's 9th from the top.
I think workaround with installing Bower and the same packages is not an option, because initially and with each framework update you must manually synchronize packages with their versions and override some configuration. Also some extensions require javascript plugins and using composer asset plugin too. So you have to do the same with each of them too. It simply not worth it. And having account on Github for web developer nowadays is kind of de facto standard.
Just create Github account if you are still don't have one and everything should be fine. Earlier updating process was pretty slow, now it's faster and I found this approach pretty interesting and flexible.
I'm new to running a Linux server and slowly getting up to speed with things.
I have already installed nginx via the apt-get function, although I'm following a tutorial which recommends installing it as a ruby gem instead.
Is there any difference in the functionality/limitations to installing it as a gem than by using apt-get? - I'm worried that it won't work for non-ruby applications if it is gem installed?
Is there any difference in the functionality/limitations to installing it as a gem than by using apt-get? - I'm worried that it won't work for non-ruby applications if it is gem installed?
There aren't any limitations on the version of Nginx that Passenger installs for you. You should be able to use it with other languages as you normally would (providing you know how to configure Nginx.) I was able to use it to connect to both Ruby and Node.js sites with no problems.
The people at Phusion have a nice page explaining why they are forced to provide their own version of Nginx (rather than using the standalone one) and it comes down to the fact that Nginx does not allow to be extended at runtime. Extensions like Passenger must be compiled into it. See this page for more information on it: https://github.com/phusion/passenger/wiki/Why-can%27t-Phusion-Passenger-extend-my-existing-Nginx%3F
(Note: When I tested this I used the installation instructions from the Phusion web site https://www.phusionpassenger.com/documentation/Users%20guide%20Nginx.html#install_on_debian_ubuntu , rather than the gem that is indicated in your tutorial, but I suspect they are both equivalent.)
I have run into this too. Where I am recommended to use one package manager over the other. I would question the age of the tutorial first, if it is not relatively recent you may want to consider if the information is no longer up to date. The libraries installed with that method may not be up to date.
However, if you intend to follow through with the tutorial you may end up needing it installed as the tutorial describes.
The difference is that one may not have all the libraries that are required or may not have the most up to date version. One tool could be buggy, I don't think this is the case in your situation but it is in Macports v.s Homebrew in my opinion. It might install to a different directory based on what install method you use, if you use a method off the web and then go back to the tutorial it could be installed to a different location then your tutorial expects.
If you have to follow the tutorial then I would all the way through, but if you don't need to use the preferred method that the program/library maintainers recommend. If the tutorial is out of date you could try to find an up to date tutorial.
good luck!
There are some bugs in django-registration0.8, that's why it installed 0.9 version manually throw ssh and also places newer version of registration directly near my scripts (under registration folder). However, django still users an old version. I'm trying to source ..\virtaulenv and then pip uninstall that package, but get Permission denied error.
What would you recommend me?
That should have worked. Here's a forum thread that walks through a quick example of uninstalling django (fist comment): https://www.openshift.com/forums/openshift/socjalregistration
If it's still failing, can you post your steps to reproduce the error and the error itself? Feel free to use the forums, or follow up here.