The Ortus BlogBox

"Ortus: A rise, beginning, coming into being, born, the origin!"

 

 

Category Filtering: 'news'

 

Ortus Jobs: We need a DevOps Engineer

Luis Majano
Mar 06, 2017

 

We are in need of a DevOps Engineer at Ortus Solutions and we would love to have you join our 100% remote and global team! So it doesn't matter if you live in a beautiful Hawaiian beach or an icy patch of land in New Hampshire. If you know your DevOps, we need to talk. Below you can find the opportunity and you can send us your resumes to lmajano@ortussolutions.com.

Dev Ops System Engineer

This is a part-time to full-time contracting position with the Ortus Solutions team as a dev ops system engineer. You will be joining a team of engineers and software developers focused on building scalable software and mobile solutions for customers around the world. This position will require hands-on knowledge of highly scalable web infrastructures and implementations, along-side server and application maintenance, debugging and implementations.

Responsibilities

  • Installing hardware and software, maintaining appropriate maintenance levels and tuning. Performing system software upgrades including planning / scheduling, testing, and coordination, and maintaining integrity of the operating system environment.
  • Problem solving for interoperability of systems
  • Responding to outages both during normal business hours and in an after-hours, on-call capacity.
  • Evaluating, recommending, installing and configuring hardware and software to meet customer requirements
  • Provide project leadership and develop solutions to improve the environment and enhance service reliability
  • Manage Nginx load balancers and web servers
  • Mange ColdFusion (Adobe+Lucee+CommandBox) and servlet container (tomcat/undertow) application servers
  • Do weekly server patching, hardening and software audits
  • Help the engineering team diagnose and solve issues that involve hardware or OS level binaries
  • Log management, server monitoring and visibility
  • Manage Bitbucket/Gitlab servers
  • Manage Jira Cloud servers
  • Manage and direct our container strategy via docker containers and Kubernetes
  • Managing our virtual infrastructures based on Xen Server
  • Co-Designing networks and system solutions based on customer requests and needs with our engineering team
  • Producing documentation for use in configuration, repair and troubleshooting of hardware, software and network operating systems

Desired Skills & Experience

  • Strong understanding of Linux especially Ubuntu, CoreOS, CentOS, Hypervisors and containers
  • Strong understanding and usage of web servers like Apache and Nginx
  • Strong understanding of load balancers either hardware or software, preferably software via Nginx+ and/or HAProxy
  • Strong understanding of docker, containers, and Kubernetes.
  • Strong understanding of cloud services like Amazon AWS, Rackspace, Open Stack, Google Cloud etc.
  • Experience with servlet containers like Tomcat, Undertow, Jetty
  • Experience with CFML Engines: Adobe ColdFusion, Lucee
  • Experience with RDBMS but mostly MySQL Databases with replication
  • Experience with NoSQL databases but most specifically Couchbase NoSQL server
  • Experience with Jenkins, Travis and automated deployment solutions and continuous integration solutions
  • Experience with source control systems like Git and SVN
  • Network Diagramming tools and experience
  • Having programming skills is highly recognized either Java, ColdFusion, PHP, Groovy, Python, Ruby, etc.
  • Experience with Software Development Life Cycles based on Agile/Scrum development

Non-Technical Skills

  • Excellent communication skills both verbal and written
  • Good organizational and planning skills
  • Good problem solving and team player
  • Proficiency in other languages other than English is highly desired

Minimum Qualifications

  • BA/BS degree or equivalent experience (5+ years)
  • US citizen, resident or green card holder
  • Flexibility in working hours

Compensation

  • Hourly rate to be determined upon qualifications
  • Remote Worker
Jobs, News 0

New Ortus Quick API Docs Explorer

Luis Majano
Feb 16, 2017

 

We are excited to announce an update to our quick docs API module. You can find our new UI and new API docs collections in the same address apidocs.coldbox.org. However, we will be migrating them to the Ortus Solutions website in the coming weeks. The update includes lots of visual and searching improvements for any API documentation created by DocBox, our API documentation library.

News 0

ContentBox 3.1.0 Released

Gavin Pickin
Jan 12, 2017

 

ContentBox 3.1.0 is a minor release with over 40 issues, improvements and new features addressed. Below you will find the detailed release notes about this release but also the major areas of improvement and new features introduced. Enjoy!

ContentBox CMS, News, Releases 0

CommandBox 3.5.0 Released

Brad Wood
Jan 10, 2017

 

We are pleased to announce the final release of CommandBox 3.5.0.  This is a minor release, with 53 completed tickets-- most of which are server enhancements focused on making server management and configuration easy across any engine.  This version has been in release candidate for a few weeks and has received a lot of testing.  As a minor release, there are no compatibility-breaking changes to any of the public APIs, but there has been some necessary restructuring of the back end bits related to starting servers that could possibly have an effect on you if you have any scripts or custom modules based on the previous folder structure of some server installs.  We recommend all users upgrade to this new version, but take a minute to review the changes so you can fully utilize the new features.

CommandBox, News, Releases 0

CommandBox 3.5 Release Candidate Ready for Testing

Brad Wood
Dec 28, 2016

 

We've been hard at work on the latest version of CommandBox which brings bug fixes, improvements, and new options for deploying and starting servers.  We think it's ready for the general public to give it a good testing before we release it so today we're announcing the CommandBox 3.5.0-rc (release candidate) for you to give a spin.  This should be a painless switch so we encourage you to take a look and provide us with feedback.  We are also pleased t have several features and fixes in this release that were provided by community members as part of our first 1000 open source pulls.

 

CommandBox, News, Releases 0

Call For Speakers Open for Into The Box 2017

Brad Wood
Nov 30, 2016

 

We're gearing up to bring Into The Box back-- our yearly Ortus conference of Boxy goodness.  This year will have some major changes from previous years.

Into The Box, News 0

Ortus Open Source Projects Celebrate 1000 Pull Requests!

Brad Wood
Nov 29, 2016

 

1000 Pulls and Counting...

Ortus Solutions maintains a growing number of open source projects that are available to the community for collaboration.  This includes everything from MVC to CLI tools, CMS, modules, and the documentation itself.  We host all our projects on GitHub and encourage the community to contribute in big and small ways.  

We are extremely proud of the CFML Community this week as we have rolled over a giant milestone by closing our 1000th pull request to our open source repositories.  This is a combined number spanning all of our 127 open source repositories including:

Thank You!

This represents many hours of work by the CFML community and we are so proud to be a part.  A huge thanks to everyone who has contributed to one of our products no matter how big or small.  The Box suite of libraries is demonstrably the most active in the CF space and we're looking ahead to a great future of community collaboration.  If you're interested in becoming a part of this effort, we'd love to have you on board.  You can read up on how to submit a pull request to one of our projects here.

And finally, if you'd like to see the full list of 1000 pulls, you can click here.  

 

ColdFusion, Community, News 0

ColdBox 4.3.0 Released

Luis Majano
Oct 19, 2016

 

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.

CacheBox, ColdBox MVC, ColdFusion, CommandBox, News, Releases, WireBox 0

CommandBox 3.3.0 Released - server enhancements and bug fixes.

Brad Wood
Oct 09, 2016

 

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 implementation, adding features, and of course, fixing bugs.  A big thanks to Denny Valiant and his work on Runwar, which is the library that makes CommandBox's severs work.

Download it

You can download the latest binary from our CommandBox product home page:

CommandBox Download

We've also updated our CommandBox documentation book to cover all these new features which can be found here:

CommandBox GitBook Documentation

Remember, you can send pull requests via Github for any typos or missing content you find in our GitBooks!  

The Command API Docs also show the latest commands and usage too:

CommandBox Command API Documentation

What's New?

Let's take a quick peek at the major new features in CommandBox 3.3

Server Enhancements

The embedded CommandBox server have seen a number of nice enhancements to make it easier for you to use CommandBox for super easy local development.

Fusion Reactor Module

The more people begin to use CommandBox for local development, the more interested they became in being able to run FusionReactor on their dev servers to help trouble shoot their code.  That's why we created a CommandBox FusionReactor module.  It's not part of the core, but can be installed in a single command and will attach FusionReactor's server monitor to every server you start.  You'll need to have a FusionReactor license or sign up for a trial to use it.

install commandbox-fusionreactor
fr register "your FR license key"
server start
fr open

Web Aliases

CommandBox allows you to create web aliases for the web server that are similar to virtual directories. The alias path is relative to the web root, but can point to any folder on the hard drive. Aliases can be used for static or CFM files.  To configure aliases for your server, create an object under web called alises. The keys are the web-accessible virtual paths and the corresponding values are the relative or absolute path to the folder the alias points to.

Here's what your server.json might look like.

{
  "web" : {
    "aliases" : {
      "/foo" : "../bar",
      "/js" : "C:\static\shared\javascript"
    }
  }
}


Here's how to create aliases from the server set command:

server set web.aliases./foo = bar

Custom Error Pages

You can customize the error page that CommandBox servers return. You can have a setting for each status code including a default error page to be used if no other setting applies.
Create an errorPages object inside the web object in your server.json where each key is the status code integer or the word default and the value is a relative (to the web root) path to be loaded for that status code.
This is what you server.json might look like:

{
  "web" : {
    "errorPages" : {
      "404" : "/path/to/404.html",
      "500" : "/path/to/500.html",
      "default" : "/path/to/default.html"
    }
  }
}


You can set error pages via the server set command like this:

server set web.aliases.404=/missing.htm

Custom tray menu items

You can customize these tray menus and add your own option for your convenience.  To add a menu contribution to an individual server, add the following to your server.json:

{
  "trayOptions":[
    {
      "label":"Foo",
      "action":"openbrowser",
      "url":"http://${Setting: runwar.host not found}:${Setting: runwar.port not found}/foobar.cfm",
      "disabled":false,
      "image":"/path/to/image.png"
    }
  ]
}

Tray menu makeover

We've updated to a new library that creates the tray icon for your running servers and the menu that appears when you right click.  In addition to better support for some Linux distros, we've added some nice new icons to the menus.

Pre/Post package scripts

Before any package script is run, CommandBox will look for another package script with the same name, but prefixed with pre. After any package script is run, CommandBox will look for another package script with the same name, but prefixed with Post. So if you have a package that contains 3 package scripts: foo, preFoo, and postFoo, they will run in this order.

  1. preFoo
  2. foo
  3. postFoo

This works for built-in package script names as well as as doc package scripts. It also works on any level. In the example above, if you created a 4th package script called prePreFoo, it would run prior to preFoo.

Better ForgeBox Login management

If you use more than one ForgeBox login, perhaps a personal one and a company one, it can be a pain to keep logging in.  It's also hard to remember the last user you logged in with.  We've introduced two new commands to help with this.  Run this to tell you who you are logged in as:

forgebox whoami

Run this to switch between users that you've previously logged in with:

forgebox use myUser

onRelease interceptor/package script

We've added a new "onRelease" interceptor and package script to help with the workflow of publishing packages.  Here's a run down of the three key points when bumping a package version.

  • preVersion - Announced before the new version is set using the bump command
  • postVersion - Announced after the new version using the bump command but before the Git repo is tagged.
  • onRelease - Announced after a new version is set using the bump command and after the Git repo is tagged.

Here is a typical package script work flow for working with a package that's hosted on GitHub and published to ForgeBox:

"scripts":{
  "preVersion":"testbox run",
  "postVersion":"package set location='gituser/repov#`package version`'",
  "postPublish":"!git push --follow-tags"
}

Then when you want to publish a new version of your package, commit your changes to Git and run the following commands:

bump --minor
publish

Those two commands, in combination with your package scripts, would accomplish the following:

  1. Run the package's test suite (a failure will abort the process)
  2. Increase the minor version of the page
  3. Tag the Git repo
  4. Change the package's location property in box.json to point to the new tag
  5. Commit the tag and new box.json
  6. Publish the package to ForgeBox
  7. Push the new box.json and Git tag

onInstall interceptor/package script

Announced while a package is being installed, after the package endpoint and installation directory has been resolved but before the actual installation occurs. This allows you to override things like the installation directory based on package type. Any values updated in the interceptData struct will override what the install command uses.

CLI Engine Update

The Lucee version that the CLI runs on has been updated to be 4.5.3.020 which is also now the default engine to be used when you use the "server start" command and don't specify a cfengine.  If you still want to start a web server on Lucee 4.5.2.018, then simply to this:

start cfengine=lucee@4.5.2+018

Release Notes

There are tons of little bug fixes in this version that you can view in our release notes.  

Bug

  • [COMMANDBOX-187] - error when updating forgebox when slugname changes
  • [COMMANDBOX-422] - Empty command CFCs with no functions throw an error starting box
  • [COMMANDBOX-423] - Error "key [FUNCTIONS] doesn't exist" thrown when trying to start command box
  • [COMMANDBOX-426] - server name completion errors on server open command
  • [COMMANDBOX-434] - Document the resolvePath() differing behaviour on OSX vs Windows
  • [COMMANDBOX-435] - artifacts clean fails on OSX when there's .DS_Store files
  • [COMMANDBOX-437] - appSkeleton in the coldbox create app wizard needs to comply to IDs instead of local disk
  • [COMMANDBOX-449] - "server open" always opens localhost
  • [COMMANDBOX-451] - The trayicon in server.json does not work with relative paths
  • [COMMANDBOX-464] - update command doesn't respect original install path
  • [COMMANDBOX-465] - custom url rewrite location doesn't respect starting server by name in different location
  • [COMMANDBOX-466] - coldbox create crud doesn't work on Windows

New Feature

  • [COMMANDBOX-316] - Add Fusion Reactor support for server
  • [COMMANDBOX-399] - Starting server in web root with WEB-INF treats CWD as war
  • [COMMANDBOX-416] - Add "open" flag to touch/new command.
  • [COMMANDBOX-430] - forgebox whoami command to show what user your API key is set to
  • [COMMANDBOX-431] - Update the storage of the APIkey in the commandbox settings to include multiple keys
  • [COMMANDBOX-432] - Have a forgebox use {username} command to switch the current api key
  • [COMMANDBOX-445] - Allow aliases (virtual directory) in web server
  • [COMMANDBOX-458] - Provide custom 40x and 50x error pages for servers

Improvement

CommandBox, News, Releases 0

New Adobe and Lucee CF Engines available for CommandBox

Brad Wood
Sep 29, 2016

 

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)
ColdFusion, CommandBox, News 0
1 2 3 4 5 6 ... 55 >>