Some dev:log 🙂️️️️️️

https://www.reddit.com/r/taskviewhs/comments/1mgvdif/dev_log_refactoring_my_api_arktype_drizzle/

Hi everyone! 🎉
I’ve just published Docker containers for TaskView (self-hosted). Now you can easily run the TaskView API Server on your own servers or local machines.

📖 Installation guide and requirements: https://taskview.tech/docs/installation

💬 If you have any questions, feel free to join the chat: https://t.me/chat_handscream/
Thanks 🙌

Hi! I’ve decided to start a blog about developing TaskView. First post available here https://taskview.tech/blog/releases/1.14.2

Hi everyone!
In the upcoming update, you’ll get the ability to organize your tasks in a more visual and intuitive way through the Graph view.

This format helps you:

see the relationships between tasks within a project;

better understand the overall picture and priorities;

identify and organize bottlenecks and dependent tasks;

plan your work not as a list, but through the connections and logic of the project.

The Graph view is perfect for those who think visually and want to manage projects not only through lists or Kanban boards but also through a network of connections.

In the next post, I’ll show what features are available and how to use them I’ve tried to make everything as intuitive as possible.

I want to share a bit about my weekend plans. Now that I’ve implemented the Graph View for visualizing task connections, it’s time for the next step something that will speed up future development and make TaskView more flexible overall.

This weekend, I’ll be working on a public API library for TaskView.

What will it bring?

Users will be able to easily call TaskView functions directly.

It will enable all kinds of integrations with other tools and systems.

It will help me develop new features faster and with better structure.

I’m really excited about this step it’s not a flashy feature, but it’s an important. I hope to finish it this weekend.

Hi! I’ve built a simple app you can try it here:
https://lifechart.handscream.com/

LifeChart shows your life week by week and helps you clearly see that the things you truly want to do shouldn’t be postponed.
I’d appreciate any feedback!

Hey everyone!

I wanted to share a bit about what has been happening with TaskView. Over the past few weeks, I have spent a lot of free time in the codebase: cleaning up old solutions, removing things that are no longer needed, and rewriting parts that clearly needed attention. I am simply trying to put everything in order so that one day I will not feel embarrassed (not 100% but I will try) opening the doors to the project.

To be honest, I have been thinking for a long time about whether I should make the code open. This project has lived several lives, gone through a few architectures, and carries its own share of quirks 🙂 But at some point I realized the following if I want TaskView to remain honest, transparent, and alive then hiding the code does not feel right.

So the decision is this: the code will be opened, and the project will be available for free non-commercial use. Not for hype, and not to prove anything to anyone I simply want anyone interested in TaskView to be able to look inside, get inspired, offer feedback, or even help.

I am not giving a release date I am moving step by step (unfortunately, free time is limited). But with each step, TaskView becomes cleaner, clearer, and closer to the state in which I can finally say: (Yes, now I can show it.) And honestly, that makes me very happy.

Thank you for being here and for following the project’s development. It truly means a lot to me 🙂

I’ve made TaskView Community Edition source-available.

TaskView is a self-hosted project and task management system focused on clarity, ownership, and control.

With the Community Edition you can:

self-host TaskView on your own infrastructure

use it for personal and internal team work

explore and modify the source code

The license is source-available:

SaaS / managed hosting for third parties is not allowed

creating competing commercial products is not allowed

The goal is simple:
give users transparency and control, while keeping a sustainable path for the project.

Repository and documentation are now public.
Feedback and discussions are welcome.

Documentation: https://taskview.tech/docs/

Docker images: https://hub.docker.com/u/gimanhead

The source code is available: https://github.com/Gimanh/taskview-community

you can build your own version from source (instructions are in README.md)

Hi! I have created Login with Google and Login with GitHub functionality, will be available after publishing in the stores here is Merge request. https://github.com/Gimanh/taskview-community/pull/8

TaskView GitHub + GitLab integrations v1.24.0

## Release Notes

### Integrations

Added integration with GitHub and GitLab.

Current synchronization capabilities:
- title and description are synchronized
- GitHub / GitLab are the source of truth
- the issue description is stored in TaskView note

### Permissions

Server API now includes permission handling for operations with the graph.

Two new permissions were added for integrations:

- integrations_can_manage
- integrations_can_view

⚠️ These permissions must be enabled manually if you want other users to view or manage integrations.

### UI Improvements

- added date placeholders when selecting dates:
- "This week"
- current month
- fixed loader display issues
- date updates are now performed with a single request
- several general UI improvements
- fixed an issue with disabled checkbox on the main screen

### Updates

- updated Web and Mobile versions

---

## Integration Setup

To enable integrations you need to add the following environment variables:

GITHUB_INTEGRATION_CLIENT_ID=<your-client-id>
GITHUB_INTEGRATION_CLIENT_SECRET=<your-client-secret>
GITHUB_INTEGRATION_CALLBACK_URL=http://localhost:1401/module/integrations/oauth/github/callback

GITLAB_INTEGRATION_CLIENT_ID=<your-application-id>
GITLAB_INTEGRATION_CLIENT_SECRET=<your-secret>
GITLAB_INTEGRATION_CALLBACK_URL=http://localhost:1401/module/integrations/oauth/gitlab/callback

Generate Encryption Key

Tokens are encrypted with AES-256-GCM. You need a 32-byte hex key (64 characters):

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

Add it to .env.taskview:

ENCRYPTION_KEY=<your-64-char-hex-key>

Hi everyone new version of TaskView released
https://taskview.tech/changelog <= here is changelog
https://taskview.tech/docs <= here is docs