Hey, everyone, and welcome back for another deep dive with us.
Today, we're going to be taking a look at Vikunja.
Vikunja.
Vikunja, yeah.
Yeah.
It's this open source, self-hostable to-do app that, well,
we're going to see if it can maybe help you get organized.
But first, a real quick shout out to our sponsor, Safe Server.
Yes.
So if you are thinking about self-hosting software
like Vikunja, these are the folks that you need to talk to.
Absolutely.
They can help you with hosting solutions and all sorts
of digital transformation needs.
Yeah.
And you can check them out at www.safeserver.de.
Perfect.
All right, so back to Vikunja.
Right.
We've got their website.
And we also have taken a peek into their code over on Getea.
Oh, very nice.
Which is where they keep their kite public.
It's a great way to see what Vikunja does,
but also the thinking behind it.
OK, so the Vikunja website describes itself
as a fluffy to-do app.
And I don't know about you, but that makes me think
it's something cuddly and friendly.
Not exactly what I picture when I
think about a productivity tool.
Yeah, well, it definitely sets a welcoming tone.
It does.
But fluffy aside, the important part
is open source and self-hostable.
And these are really key to what makes Vikunja so different.
Right.
So let's break that down.
For folks who haven't encountered those terms before,
what do they actually mean?
Well, open source means that the code behind the app
is open for anyone to see, change, and share.
It's like a recipe that anyone can use and tweak.
I like that.
And this transparency allows for community contributions
and a lot of flexibility.
OK.
Self-hostable, on the other hand,
means that you can run Vikunja on your own server.
Right.
So you're not relying on some big company
to keep your to-do safe and accessible.
So you're in control, which a lot of people find appealing,
especially if they're concerned about privacy.
Exactly.
And speaking of privacy, Vikunja's origin story,
as told on their website, really highlights that concern.
The founder, Konrad, started Vikunja
because he couldn't find any good open source
to-do apps that respected user privacy.
Yeah.
It's a common theme these days.
It is.
A lot of people are wanting more control over their data.
Right.
So Vikunja was born out of a need for something different,
something more in line with valuing user privacy.
But does it have the features to back that up?
Because let's be honest.
Nobody wants a to-do app that's all principles
and no functionality.
Right.
Well, looking at their website, they've
got a pretty solid set of features.
OK.
They've got project organization, task assignment,
collaboration tools, and multiple views,
like lists, Gaunt charts, Kanban boards, even tables.
Hold on.
That's a lot.
Yeah.
I mean, I get the list view.
That's pretty standard.
Right.
But Gaunt charts and Kanban boards,
those are more project management tools, right?
They are.
But think about how useful that could be.
So let's say you're planning a trip.
You could use the list view for packing.
Makes sense.
The Gaunt chart for scheduling your itinerary,
and the Kanban board to track your progress on booking
flights and accommodations.
So Vikunja lets you choose the view
that best suits your needs for each task or project.
All right.
I'm starting to see the appeal.
OK, good.
So it's not just about listing out tasks.
It's about managing projects, even collaborating
with others.
But they mentioned two options for using Vikunja, the Vikunja
Cloud or self-hosting.
Yeah.
So what's the difference, and which one should someone choose?
That's a good question.
Yeah.
Well, Vikunja Cloud is definitely the easiest option.
OK.
You just sign up, and they handle all the technical stuff.
Right.
So it's great for people who just want a simple, hassle-free
experience.
But if you're a control freak like me
and want to manage everything yourself,
self-hosting is the way to go right.
Probably, yeah.
What are the downsides there, though?
Well, you're responsible for setup, maintenance,
and security.
OK.
And that can be a bit daunting for beginners.
Right.
But if you're comfortable with the technical side,
self-hosting gives you complete control over your data
and how Vikunja runs.
So convenience versus control.
Exactly.
Makes sense.
And speaking of the technical side,
we've got a glimpse into Vikunja's code repository
on GitEa.
Over 10,965 commits, which, to someone like me,
sounds like a lot of code.
It is a lot of code.
It is.
Yeah.
But it shows how active the development is.
That's it.
One interesting commit I found was
about switching to a smaller base
image for their Docker container.
OK.
This basically means they're trying
to make Vikunja more secure by reducing
potential vulnerabilities.
So they're not just focused on adding fancy features.
They're also thinking about practical things,
like security.
Right.
And they're very transparent about it.
That's good.
Which is a hallmark of open source projects.
OK.
They even have buy me a coffee and sponsorship options
on their website.
I did see that.
Which suggests they're trying to build something sustainable
independently.
Yeah, that makes sense.
Yeah.
So it seems like they're building Vikunja
with a clear focus on user privacy,
a robust set of features, and a commitment
to being open and transparent.
It's definitely an intriguing option
for anyone looking to take control of their to-do list
and potentially their data.
For sure.
And it raises an important question.
What do you prioritize in your digital tools?
Convenience, control, privacy.
Yeah.
Thinking about that can really help
you decide if Vikunja is the right fit for you.
That's a good point.
It's all about finding the right tool for you
for your individual needs and values.
That's true.
Now, let's put on our developer hats for a second.
OK.
And take a closer look at how Vikunja is actually built.
All right.
We've got access to their code repository.
So let's see what's happening under the hood.
OK, so we're going from Fluffy to Techie now.
A little bit.
I'm game.
OK, good.
But remember, some of us aren't programmers.
Right.
Can you make this code stuff relatable for us?
Absolutely.
So think of the code like the blueprint for the app.
OK.
Remember those 10,965 commits we mentioned?
Yeah, that's a lot.
Each one represents a change or improvement
to that blueprint.
So it's a constantly evolving project.
Which is cool.
Yeah.
But I'm curious, what kind of language are they using?
Like, what are they speaking in this blueprint?
Well, VKUNJA is primarily built using the Go programming
language.
Go?
Go.
Yeah.
And it's known for its efficiency and its ability
to handle lots of tasks at the same time.
So it makes it a good choice for building a robust and scalable
application.
So Go is like the engine.
Yes.
What about the dashboard?
Like the part that the user actually
sees and interacts with.
Ah, that's where Vue.js comes in.
Vue.js?
Yes, it's a JavaScript framework that's
popular for building interactive interfaces.
And Vakunja uses that to create a really smooth and user
friendly experience.
So Go powers the app.
And Vue.js makes it look good and easy to use.
Exactly.
It's interesting.
Yeah.
When you were exploring the code,
did any particular pieces stand out to you?
One commit that caught my eye was
related to using something called WebSockets.
WebSockets?
Yeah.
OK, now that sounds technical.
It is a little bit technical, but bear with me.
Because it really does have a direct impact
on your experience as a user.
OK.
I'm intrigued.
Lay it on me.
What are WebSockets?
Imagine you're collaborating with someone
on a project in Vikunja.
OK.
And they update a task on their end.
Right.
With WebSockets, you would see that change instantly
on your screen without having to refresh the page.
Oh, so it's all about real-time updates,
keeping everything in sync.
Exactly.
I get it now.
Yeah.
That's pretty neat.
Yeah, it is.
It is.
It makes collaboration much smoother.
Right.
Now, while all these technical details are fascinating,
I think it's important to sort of zoom out
and see how this translates to a better experience for you
as the user.
Right.
Vikunja's developers are clearly paying
a lot of attention to the details,
both in terms of features and the underlying code.
Yeah, and that's reassuring, especially
when you're considering trusting
your to-dos to an app.
Absolutely.
Speaking of which, let's talk about the people
behind Vikunja.
Yes.
The community.
These seem to be a pretty big part
of what makes this project tick.
They are the lifeblood of Vikunja.
Yeah.
Open source projects thrive on their communities,
and Vikunja has a really incredible, active,
and welcoming community.
OK, so we've got the fluffy mascot, the clean code,
and now a bunch of friendly people.
That's right.
I'm starting to see why people like this Vikunja thing.
Good.
But what does a community for a to-do app actually look like?
What are they doing?
Well, it's not just about chit-chatting about to-do lists.
People contribute in all sorts of ways.
Coding, documentation, translations, testing.
Some people even just help by spreading
the word about Vikunja.
So it's a real team effort.
It is.
With everyone chipping in to make the project better.
That's impressive.
I'm guessing this community has a home base somewhere online.
They sure do.
Vikunja has a really active forum
where users can ask questions, share ideas, report bugs,
and connect with each other.
Also, it's like a virtual town square for all things Vikunja.
Exactly.
Love that.
And for folks who prefer something a little more
real-time, they have a chat platform too, right?
Yes.
They use Matrix for real-time conversations.
Matrix.
It's great for getting quick answers or having
more informal discussions.
So they've got all the bases covered.
They do.
That's fantastic.
Yeah.
It's inspiring to see so many people coming together
to create something that's not only useful but also reflects
their values around open source and privacy.
It really is.
And this community is a big part of why Vakunja can
stay true to those values.
That makes sense.
Yeah.
They even have buy me a coffee and sponsorship options
on their website, which shows their commitment
to staying independent and community driven.
Yeah.
That makes a lot of sense.
They're not beholden to some big corporation dictating
what features to add or how to handle user data.
Exactly.
Before we move on, I just want to remind everyone
that we'll have links to all these community resources
in the show notes.
So don't worry about trying to remember everything right now.
And if you're thinking about self-hosting Vikunja,
remember our sponsor, Safe Server.
Oh, yeah.
They can help you set everything up
and make sure things run smoothly.
That's right.
Visit them at www.safeserver.de for more information.
Great point.
Yeah.
Now, as we wrap up this part of our deep dive,
what's the one key takeaway you hope
our listeners are getting about the Vikunja community?
For me, it's the collaborative spirit.
It feels like everyone involved from the developers
to the users is invested in making
Vikunja the best it can be.
I agree.
It's that shared sense of ownership and purpose
that makes open source projects so special.
Now, for those inspired to get involved,
how can they contribute to the Vikunja project?
And that's a great question.
I imagine there are folks listening
who might be thinking, hey, I have some coding skills,
or I'm great at writing documentation,
or maybe I just want to spread the word.
What are their options?
Well, if you're a coder, you can jump right
into the code repository on Kitea
and submit what are called pull requests.
Pull requests.
Yeah, that's basically how you propose
changes or new features.
OK, so that's for the tech savvy folks.
Right.
But what about those of us who aren't programmers?
Yeah.
Are there ways to contribute without needing to know code?
Absolutely.
There are tons of non-coding contributions
that are just as valuable.
You could help with writing or translating documentation,
testing new features, or even just spreading the word
about Vikunja on social media.
So even if you're not a tech wizard,
you can still make a difference.
Exactly.
And for those who want to support the project
financially, there's always the option
to buy the developers a coffee or become a sponsor.
Exactly.
Every little bit helps to keep the project going.
Right.
And even if you can't contribute directly,
just using Vikunja and providing feedback is incredibly helpful.
The developers are always listening and making improvements
based on what users tell them.
So even just by being an active user,
you're part of the Vikunja journey.
You are.
That's pretty cool.
Exploring Vikunja has really changed
how I think about to-do apps.
It's not just about checking boxes anymore.
It's about finding a tool that reflects your values
and empowers you to work the way you want.
I think that's a key takeaway for everyone listening.
Vikunja is more than just a to-do app.
It's a statement about taking control of your digital life
and supporting a different way of building software.
Couldn't have said it better myself.
Okay, good.
So to wrap things up,
if you're looking for a to-do app that's open, transparent,
puts you in control, check out Vikunja.
Absolutely.
Explore its features, connect with the community,
and see if it's the right fit for you.
And remember, if self-hosting sounds appealing
but a bit daunting, our sponsor Safe Server can help.
Oh, that's right.
They can guide you through the process
and provide the hosting solutions that you need.
They can.
You can find them at www.safeserver.de.
Thanks for that reminder.
And that's a wrap for our deep dive into Vikunja,
the fluffy, open source, self-hostable to-do app that's
making waves in the productivity world.
It is.
Until next time, keep exploring, keep learning,
and keep diving deep.