Add global content and objects to every view within your .Net application
Restrict controller actions to users with specific roles, and base them upon controller parameters.
I've accepted a position as Assistant Director of I.T. for Application Development at Colorado State University College of Health and Human Sciences
Introducing an API Wrapper for the RocketChat API
Handle multiple forms within multiple Django Views
Glad to announce a new book that I've reviewed is now available.
Today I am announcing the immediate availability of django-feedme 2.0. This release contains many bug fixes and feature improvements.
Lately, we've been trying to improve our testing structure around testing our API calls without actually having to make them. To do this we of course use the excellent mocking library for python.
This week while writing a new feature in the core of one our apps, I had to mock something that would be used in almost every single test in the test suite. I'm a huge fan of keeping things DRY so you can imagine that when I started to type things like this:
Join me for a talk next week at the Fort Collins Digital workshop for a short talk on the Django Rest Framework!
Or why I feel behind all the time
It's hard to believe its already been a year since I returned to Kansas State on the webteam. Throughout this year we've accomplished a lot and I wanted to reflect on some of those things.
I've released new version of django-site-notifications and django-downtime. Both these releases bring support for Python 3.x as well as bringing them up to date with at least Django 1.7.
Heads up that I'll be at PyCon this year in Montreal, Canada. If you are around and want to meetup, let me know!
The last few months I've been working on fixing up our applications at K-State and how they interact with other custom built and off the shelf software. One of our common practices on the web team is to create applications that consume data from other organizations on campus, manipulate it, display it, etc. One of the things I noticed early on was that we would use the same boilerplate code to generate and get responses from various systems. None of the calls were tied together, and we often used the same or similar data in multiple apps. Something had to be done.
Join me for a talk tomorrow at the Fort Collins Digital workshop for a short talk on Salt with demos!
Come join in my discussion on Async processing with Django and Celery this Monday August 11 in Fort Collins CO. I'll be going over the basics of using async processing and tips for utilizing this type of architecture.
In any team environment, a developer may have to adapt another's code. When they fail to understand it, they condemn it. This attitude isn't helpful, in fact it's hurtful.
I've recently come across a few stumbling blocks where bad code got deployed, caused some damage, and then required a roll back or quick modification and hotfixes. While I have always written some amount of tests for the last few years, I've never been a huge fan of test driven development. The very idea that I have to spend hours writing up tests and mocking things to then spend just an hour or two writing the code to fix the issue seemed somewhat backwards to me and not an efficient use of my time. To a certain degree I think this somewhat depends on the scale your site is at and the affect it could have on any visitors or customers of your site. The larger your code base, and the sheer scale of your audience greatly affects the rate at which your unit and integreation tests begin to pay huge dividends.
I wanted to give a quick overview on how I tend to use Vagrant and a brief explanation of my thought process, how I learned, and what I would do different next time.
In my short experience in the industry I've been able to learn a few lessons from my experience. My five lessons in five years are:
This is a (short) update to my post about moving to Gunicorn from mod_wsgi.
Yesterday, I had the pleasure of giving a talk at Boulder Django on Django Deployment and Hosting options. We had a good turnout and I think overall most of the attendees learned something about Django, Python, and Deployments. I've included the slides on speakerdeck below.
This week (tonight) I moved my major sites (this site, my wife's site and my brothers site) over to Gunicorn from Mod_wsgi. I initially thought it was going to be an incredibly different process, but I'm here to show that it can be done in one night and it isn't nearly as hard as I thought. I wanted to document and outline the process in case anyone else wanted to make the transition.
For a while I've wanted to write and document my opinions and beliefs on web development, the process, how it could improve and how to develop software in an always changing (agile) environment.
Download the source from http://libjpeg.sourceforge.net/ Extract, configure, make: tar zxvf jpegsrc.v6b.tar.gz cd jpeg-6b cp /usr/share/libtool/config/config.sub . cp /usr/share/libtool/config/config.guess . ./configure --enable-shared --enable-static make
Too many times I have seen freeware open source projects start with such vigor and high expectations, only to fail or take enormous amounts of time and money. Most every time I have seen this happen its blamed on the pure fact that the software itself is free. These projects don't fail because of lack of funding, but a lack of a clear goal and the people resources behind it. I want to dive into the open source philosophy for a second and gather my thoughts.
Great read. Please note this was transcribed from http://aspnetresources.com/articles/CustomErrorPages.aspx