If you haven't purchased all your Christmas presents, it's time to made a mad dash for Amazon and reach for the quick shipping! If your stockings are already hung by the chimney with care then you'll have time for this next tidbit in our 12 Tips of (CommandBox) Christmas series. One of our goals for CommandBox is for it to become a drop-in replacement for your local dev environment with the least amount of hassle and to do that you'll likely need to create some web aliases (or virtual directories as IIS calls them).
Snuggle up with a warm cup of eggnog (if you're into that sort of thing) because here comes the 3rd installment of our 12 Tips of (CommandBox) Christmas aimed at lifting holiday spirits and empowering developers! Today we look at the sweet GitHub integrations we offer!
Today we continue our 12 Tips of (CommandBox) Christmas series aimed at bringing warmth, holiday cheer, and useful information to a cubicle near you. CommandBox does a lot of things online for you. It connects to ForgeBox, the CFML package repository, it downloads CF engines to start servers, and can even update your packages to new versions. This is great when some Starbucks Wifi is in reach, but what about at 30,000 ft or working on the road. You still need to be able to start up servers, install dependencies, kick butt, and take names (all in the Christmas spirit, of course!). Here are some clever tricks to keep you working even when the network is unplugged.
At Ortus we love the holidays and we figured the best way to get you in the Christmas mood was to share the gift of developer productivity this year. That's why we're doing a 12 Tips of (CommandBox) Christmas this year to send you into the new year with some clever tricks you can use as leverage when asking for your raise!
Love to use CommandBox but your network admins require you to use a company proxy for all your internet traffic? This can give you weird errors any time you try to install packages, search ForgeBox, or start up an Adobe server. That's because each of those items requires you to connect to the Internet.
More and more people are starting to use CommandBox for their local development, especially among teams who want to quickly and easily start up the same environment on each of their machines. That has led to the most common question now for CommandBox users which is: "How do I automatically configure my ColdFusion/Lucee settings on my server?"
This is a fair question, and for the most part I've treated configuring the settings in your CF engine to be outside the realm of what CommandBox tries to solve. The reality is, the CF engines often times fall short and people need a better way. Here's a guide for your current options when it comes to configuring the settings on your CF engine.
We are pleased to announce the general availability of ColdBox 4.3.0, WireBox 4.3.0, CacheBox 4.3.0 and LogBox 4.3.0. This is a minor release with some great improvements and lots of bug fixes. So let's look at the major things in this release.
We are pleased to announce a minor release of our CommandBox CLI, server, and package manager tool today. Version 3.3.0 of CommandBox is our second minor release since we added support for starting Adobe ColdFusion engines, Railo, and Lucee 5 web servers. This release has 46 tickets that focus on cleaning up more rough edges around the server implementatio...
We've updated ForgeBox.io to have updated CF Engines for Adobe ColdFusion as well as Lucee Server to include some recent security fixes from each as well as some new yet-to-be-released Lucee features.
Here are the new Adobe ColdFusion versions:
- ColdFusion 11 Update 21 (10.0.21+300068)
- ColdFusion 11 Update 10 (11.0.10+300066)
Here are the new Lucee Server versions
- Lucee 4.5 Stable (4.5.3+020)
- Lucee 5.0 Stable (5.0.0+254)
- Lucee 5.0 Snapshot (5.0.1-snapshot+067)
- Lucee 5.1 Beta 2 (5.1.0-beta.2+031)