Hey thanks, I was properly looking into WebDAV yesterday, should be simple enough to implement, just making sure I don’t add features for the sake of it, once I’m certain it’s the right way to go I’ll implement it properly, for now my biggest aim is to get the tool as stable as possible ♥️

Thank you so much! Let me know how you get on!

Thank you, this is awesome! I’ll have a proper investigation and decide what route to go to, I don’t know enough about WebDAV and I like to make studied choices, you gave me a lot to think about and that’s great!🙌

Hey! Yeah as long as you set the folder to the right permissions :) And I am a bit torn between WebDAV or straight websocket as it already allows file manipulation straight from the UI, so may be easier to have a socket server for collaborations

Glad you like it ♥️

Oh wow, that definitely threw me off lol anyhow, I don’t think I am more knowledgeable than you at all, I just know the tool I built more, so I can help figure out the nuances of it…

I have a feeling nsenter is not liking your nas for some reason, I wanna try a workaround and if it works for you I’ll go through the code and sort it out so we can use a proper env variable for this

add this env variable for now and tell me if it sorts you out <3

environment:
  - PATH=/usr/bin:/bin:/usr/local/bin:/usr/sbin:/sbin:$PATH

Meh, I want to make sure things work, that’s also part of the promo right? haha

run which crontab for me? I can see cron is running but I still am not sure you have crontab installed on the host machine if that makes sense

Hi, I went through your logs and it seems like crontab is not installed on the host machine?

stderr: 'sh: 1: crontab: not found'

The tool uses the host crontab command via nsenter to manage cronjobs, so it only works if ran from hosts that leverage crontab to run cron jobs.

If that’s not the issue let me know and we can try and debug it together further, but looking at the logs it really seems like crontab is just not installed on your nas (guessing it’s a nas looking at the volume1 path)

p.s.

Thank you for the screenshots acknowledgment, I absolutely hate not having a visual aid on repositories when I want to try a new tool, I like to see what I am getting into before I get into it, and I absolutely judge a book by its cover, I am a frontend tech lead, UI is extremely important to me, if an app doesn’t have a somewhat clean UI I kinda refuse to even try using it hahah

Hi, haven’t tried to run it with proxmox as I never managed to get into it, but yes, it does support multiple users (there’s an env variable for that) and you can filter them easily via the UI ♥️

Hey! Glad everything is working smoothly for you ♥️

Yeah I keep meaning to fix that and I keep forgetting, I’ll do my best to remember to add that on the next release >.>

Yeah this is one of the most requested features so far, I’ll need to add offline caching eventually so the PWA can still work offline. At the moment it does work if you only have it connected internally, but in the moment it can’t communicate to your server it’ll go down, yes.

jo.tt

if only I had ~1600£/year to throw on a domain… hahaha

Thank you btw, I won’t always be able to be this responsive, but it’s some exciting time with the rebranding going on. I usually respond within the day tho, especially if I deem something to be fairly urgent :)

No, it does not, but I don’t think it should be too hard to implement (at least the checklists side of thing - kanban board subtasks may be a whole can of worms UI wise, but can look into it) raise an issue on github and I’ll look into it as soon as I can fit in the roadmap <3

Oh yeah, that’s not a feature yet. There’s an open feature request for this and I’ll definitely implement it, may take a bit of time to do.

Would you be able to give me a couple of screenshots on what the context looks like? I just had a simple “mentioned 2 times” with links on where it was mentioned in mind, but full on context sounds way better, I’m curious to see how that works (totally not copying :P)

I mean, I don’t use it so I can’t really say much on the topic, when looking into it yesterday I found this article https://signal.org/blog/signal-is-expensive/ which kinda goes through some of the stack they use, and in all fairness they do mention aws in the mix, so it’s not like they were keeping it hidden or anything, it’d be valuable for a company who values privacy so much to be a little more upfront on what’s used for what but as you’re probably well aware we don’t - and never will - live in a perfect world do we haha

Aw not silly at all, maybe I should make it clearer actually. Always important to remember that what’s obvious to me may not be as obvious to someone else

Hi! Thank you, I’ll create a post there now!

Hi! Very glad you like it! It already is editable :) it’s done via the admin panel ♥️ you can even set the pwa icon if you wished to

Hey, for as much as I genuinely think docker is the way to go for this kind of things you don’t HAVE to, you can just run it as a service, the readme has a manual install process on top of the docker one.

Also if you use proxmox there is a community script going around for ease of setup ♥️

Should be back, of course everything went down while I was asleep, the joys 🤦‍♂️ By back linking you mean offline cache that links to a server when back online? If so, no, not yet at least