When deploying an instance within the Amazon Cloud, one can usually specify how to configure the instance during creation. However, not all instances support this so easily and Citrix Netscaler is one of those instances.
I’ve had many clients ask some variant of the question “shouldn’t this cost less?”. While there are many answers, I’ve made a list of some common cost drivers that many clients don’t consider when controlling project costs.
I’ve recently been working on a project that needed use of the spree product assembly, but the users needed to be able to choose a recipe and ingredients. I used a combination of jQuery, JSON cookies, and some modifications to the product assembly to address this issue.
Because of a recent security issue with libyaml you may see the psych error:
You appear to have an outdated version of libyaml (0.1.4) installed on your system.
Prior to 0.1.6, libyaml is vulnerable to a heap overflow exploit from malicious YAML payloads.
Recently, a colleague posted an analysis about how much time is needed to build a bare-bones Spree Commerce site, which can be found here. As a result, many potential Spree users are very excited: for less than two days of development time, someone can go from nothing to making money. That’s great!
Spree is a great Ruby on Rails e-commerce platform, allowing developers and clients to quickly set up an online store-front. A completely functional store can be built in a relatively short amount of time. Additional customization can commence from there.
Spree comes with a front end theme already installed. This allows a developer to quickly provide a working store with a usable front end. A default Spree store looks like this:
There are a lot of convoluted examples and instructions out there for adding a login system to your Rails app. You’ll never need to turn to one of those again if you just follow these 6 simple steps:
I’m creating a basic pantry application which will be able to catalog current items in the user’s pantry. So, one of the pages needed will display different food items and the current quantities in the user’s pantry. A way to organize this data is to use a Bootstrap Panel to display the current totals and when the selected panel is clicked, individual data values will be displayed.
The data structure consists of Store, Producer, and Unit models, which all just consist of a name. Next, we have the Food model which has a name, upc, servings, serving_size, and references to a Producer and Unit. Finally, we have the Stock model which has a price, quantity, discount, bought, and references to Food, Store, and User (for the User I’m just using the basic Devise User model).
Over the past few months, we’ve been making some exciting changes, growing and evolving in order to better meet our clients’ development and business needs. And the time has finally arrived to unveil one of our new developments!