I want to MANUALLY download a CFWheels Plugin - specifically https://www.forgebox.io/view/cfwheels-js-confirm I can't find a link on that page to manually download the plugin. Where can I get it?

@Brian Lang The least amount of work is really to just type

install cfwheels-js-confirm

into CommandBox. You can get the equivelant code, but that package uses a Git URL with commitish. For example, the

1.0.5

version is pulled from this location

"location": "perdjurner/cfwheels-js-confirm#v1.0.5",

(That's from the package's

box.json

) which basically means the

perdjurner/cfwheels-js-confirm

repo is cloned from Github, then the

v1.0.5

tag is checked out.

OK, how do I do that on a server where I'm not permitted to install CommandBox?

So you can basically manully clone that repo and checkout the code at that tag to get the same thing CommandBox would give you. You'd also need to manually take into account the

ignore

section in the

box.json

as well

"ignore": [
    "**/.*",
    "test",
    "tests"
  ],

Not government. Just not sure I'd get permission to run this on a production server

A good question may be why on earth you're installating things directly on a production server?

Setting up a new production server. It's not in productio nyet.

Right, but you still write code... in dev, right?

We normally use DeployHQ to upload code to our production servers normally.

Right, so whereever it is you upload it from-- that's where you'd be installing it, right?

I commit to our github repo, and DeployHQ draws from there

Right, so then it comes down to whether you • commit dependencies to the repo • only store them the

box.json

and then install them as part of your build

Yeah - no build/integration process after upload. Old-school CF didn't need it 🙂

That's fine- if you're not set up to have CommandBox on prod to pull dependencies, then I'd just go with a process where you commit them to source control.

Yeah, that's normally how it works. As this is new, I was trying to shortcut the process to start testing.

Keep in mind the advice you were given there isn't going to work on all packages

That's ok. I'm trying to upgrade a legacy 10-year old CFWheels 1.4.x on CF16 project to 2.x on CF21.

I don't really buy that. Nothing is preventing you from grabbing the CommandBox binary and tossing it on your desktop so you can run

box install asdf

😉

True. I tried it though, and didn't get the ZIP file for that plugin that CFWheels requires. CFWheels requires the ZIP file in the plugins folder and box install ... didn't pull down a ZIP file at all

The latest version of CFWheels requires a zip?

Plugins in CFWheels have always required a ZIP. That gets extracted to a folder in the plugins directory whenever you run a reload on the site

Hmm, I'm pretty sure the CFWheels devs have made it so CommandBox will install whatever it is CFWheels needs out of the box. Perhaps you didn't have the wheels CLI module installed

Hey Brad, Brian is correct that at present CFWheels plugins are always zip files that get unpacked on first load. Peter has been doing an excellent job in improving the CLI tools but the plug-ins haven't changed as of yet. Much of this is being discussed for the next 3.0 release of CFWheels.

@Brian Lang @bdw429s @David Belanger Just wanted to chime in. I understand what you are referring to but I don't use zips in plugins folder. In config/settings.cfm I have:

set(overwritePlugins=false);
set(deletePluginDirectories=false);

Then I don't need the zips. Also in commandbox when I'm in the cfwheels web root and issue

install defaultScope

it not only puts the zip in the plugins folder but extracts it too. So you don't need what I put in settings above I just do it because I personally remove the zips out of my plugins folder.

That should be added to the documentation on the page discussing Plugins

@Brian Lang Hi Brian I see it disscussed here - https://guides.cfwheels.org/cfwheels-guides/working-with-cfwheels/configuration-and-defaults#plugin-settings

Ah. I see it. A cross-reference from the Plugins page would be helpful then https://guides.cfwheels.org/cfwheels-guides/plugins/installing-and-using-plugins

Nice, thanks for all the extra info guys!

You are correct @risto that, at present, you need to customize CFWheels to not look for and expand a zip or delete the existing directory when it detects a new zip (or if the Zip has been deleted). I was speaking more of the current default scenario because today if you use CommandBox to install the plugin, it will download the zip to the directory only and CFWheels takes care of the rest on first load. If you unzip the file yourself and delete the zip without implementing the customization that @risto suggested, you'll lose whatever you commit when the framework loads. I didn't want to confused anyway which is why I mention the default behaviour. The plan being discussed for the next version is to change CFWheels to not need to Zip files and follow the standard CommandBox install which will install all the directories and files into the plugins directory based on what's inside the box.json file and remove anything previous logic relating to Zip files.