joomla/Component-Builder
joomla
/
Component-Builder
38
19
Fork 11
Code Issues 53 Pull Requests Projects 3 Releases Wiki Activity

Updated 064 How to install jcb packages (markdown)

Amigo 2019-09-27 11:50:44 +02:00
parent 0ad0d2254c
commit b790f021e0
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
064-How-to-install-jcb-packages.md

@ -11,13 +11,16 @@ This is a quick tutorial on how to install a JCB package. With the assumption th
[00:01:20](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m20s)
Once you are on the 'Backup Local Data First' page and you have yourself exported a JCB package, then this is where you can select it from your Computer, or from a directory or from a URL. With these import methods there are not a checksum validation feature in place. You will need to be sure of the integrity of that package. [00:01:44](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m44s) We cannot validate that package integrity. Since it is being selected from your desktop and you are in a your local development environment, there should be no reasons for concern. If you are pulling it from an external source then possibly you will need to be more cautious. Whereas when it comes to the VDM Packages and the JCB Community Packages, these are the areas where we are trying to add a layer of security to ensure that the package area remains as stable as possible. There is ways for you to add your own JCB Package to the community repository. <<<<<<<<<<
Once you are on the 'Backup Local Data First' page and you have yourself exported a JCB package, then this is where you can select it from your Computer, or from a directory or from a URL. With these import methods there are not a checksum validation feature in place. You will need to be sure of the integrity of that package. [00:01:44](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m44s) We cannot validate that package integrity. Since it is being selected from your desktop and you are in a your local development environment, there should be no reasons for concern. If you are pulling it from an external source then possibly you will need to be more cautious. Whereas when it comes to the VDM Packages and the JCB Community Packages, these are the areas where we are trying to add a layer of security to ensure that the package area remains as stable as possible. There is ways for you to add your own JCB Package to the community repository. <
### Tutorial Explaining Why We Will Do Things The Way We Do
[00:02:28](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m28s)
A tutorial is provided to show you how to do that. Explaining why we will do things the way we do them. The fact is that everybody will then have access to that package in this area. You can then also get free keys for the VDM packages. In the past you have to pay for them. We have decided in [00:02:55](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m55s) an initiative to show all of you exactly how JCB can work and function. We have decided to give these packages away asking you to follow few steps in supporting us by forking starring or watching these packages in their specific repositories on GitHub. If you need more guidance about this [00:03:22](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m22s) you can just click on that link. They'll show you exactly what you need to do. Once you've the key for that specific package, you can come and select that package. It only relate to some of the packages at this point. Which is the first [00:03:38](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m38s) prominent Component Builder itself. I would suspect that would be your first choice as well. Once you've selected the package you simply can click on Get Package [00:03:53](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m53s) that is been taken from GitHub and brought to your developing environment. In doing so it will run a validation on the integrity of the package, because there are checksums in place. [00:04:09](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m09s) You will need to validate the checksum manually. The way you do that, it'll show you the checksum that was used to evaluate the package integrity. Since it's passed, the validation you will know that this checksum is the one that you need to see if you open [00:04:26](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m26s) this link 'https://raw.githubusercontent.com'. Opening this link will also reveal a checksum, but at this time you will be seeing a verification By Digi Cert. It must be at least this(see video) part of the URL must be correct. [00:04:46](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m46s) This will vary from package to package, but it should have the package name. This should correspond to the value you see here. That little bit of manual effort is all you need to do to be sure that the package that you have now in your position [00:05:04](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m04s) is the original authentic package that we have distributed. At this point you're all good to go. All you need now is to take the key that we have sent you and add it to the key area.
A tutorial is provided to show you how to do that. The fact is that everybody will then have access to that package in this area. You can then also get free keys for the VDM packages. In the past you have to pay for them. We have decided in an initiative to show all of you exactly how JCB can work and function. [00:02:55](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m55s) We have decided to give these packages away asking you to follow few steps in supporting us by forking, starring or watching these packages in their specific repositories on GitHub. If you need more guidance about this you can just click on that link. [00:03:22](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m22s) They will show you exactly what you need to do once you have the key for that specific package, you can come and select that package. It only relate to some of the packages at this point which is the first prominent Component Builder itself[00:03:38](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m38s). I would suspect that would be your first choice as well. Once you have selected the package you simply can click on 'Get Package' that has been taken from GitHub and brought to your developing environment.[00:03:53](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m53s) In doing so it will run a validation on the integrity of the package, because there are checksums in place. [00:04:09](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m09s) You will need to validate the checksum manually. The way to do that; it will show you the checksum that was used to evaluate the package integrity. Since it has been passed, the validation you will know that this checksum is the one that you need to see if you open this link 'https://raw.githubusercontent.com'.[00:04:26](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m26s) Opening this link will also reveal a checksum, but at this time you will be seeing a 'Verification by: Digi Cert Inc'. It must be at least that this(see video) part of the URL must be correct. [00:04:46](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h04m46s)<<<<<<<<<<<<<<<<<
This will vary from package to package, but it should have the package name. This should correspond to the value you see here. That little bit of manual effort is all you need to do to be sure that the package that you have now in your position [00:05:04](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m04s) is the original authentic package that we have distributed. At this point you're all good to go. All you need now is to take the key that we have sent you and add it to the key area.
### Choose Merge - Change In Package / Force Local Update Works Only If Merge Is Selected