A simple service to keep your Django project dependencies up-to-date.
$12.50 per dependency, per month.
A Litiks maintenance package looks after the ongoing work of keeping your project in a good state of repair. I will ensure that your project's dependencies are kept up-to-date, and that any security patches are applied quickly. While I'm at it; I'll look after basic bugs and performance monitoring, to ensure that your code runs as smooth and as fast as the day you built it.
A maintenance package does not include any developer time for 'new work' on your project, such as adding a new feature or changing a site behaviour. If you'd like to make ongoing improvements to your django project, you may consider adding a service retainer.
Outdated dependencies can be a liability for your project. With 13 years of experience; I've been working with Django since v0.9. I understand there can be significant challenges transitioning a project to the latest version of Django, but please believe me when I tell you it is always worth it.
Here's what I'll do:
Sometimes performance issues are slow to appear.
It's easy to miss a performance faux-paux when the database only has 100 records. But 12 months and 200,000 records later; an innocent looking bit of code like
`results = list(queryset)[:10]` can become a major issue.
`results = list(queryset[:10])`
The Litiks Maintenance Package is priced at $12.50** per dependency, per month.
** This pricing is more of a guideline. Let's chat!
When determining 'what counts'; there are a few considerations. In general, a dependency is any 3rd party code which is not maintained within your project itself. A common set of dependencies might be: ubuntu, mysql-server, nginx, python, django, mysqlclient, and jquery. A total of 7 dependencies.
You can usually get an idea of the number of dependencies that your project has by reviewing the following files in your project: Dockerfile, requirements.txt, settings.py, and base.html.
Be aware that pip and node packages often define their own dependencies, which can create an enormous dependency graph. My pricing is usually tied to those dependencies which you call directly, but exceptions may be made for a dependency in your stack which is slow to apply upstream updates. If your requirements.txt file is massive, it's likely a 'frozen' snapshot of your dependencies. Try running pipdeptree to view your 'first order' dependencies.
Ultimately, this 'maintenance package' is just a suggested scope of work as you sign into a service retainer with Aaron Mader. But it doesn't have to end there. If you decide to add a new feature, or make improvements to your infrastructure, I've got you covered! I offer end-to-end services, so I'm just as comfortable discussing a new user-story with you, as I am transitioning your project to django 3.x.
I'd love to hear from you!
Are you ready? Let's talk! Send me an email at [email protected].