muddyfootprints.
Custom Container Start Command Not Working
My init command is now
bash -c 'git clone https://github.com/melembroucarlitos/pibbss-infra.git && chmod +x /pibbss-infra/daemon.sh && cp /pibbss-infra/daemon.sh /etc/init.d/idle_watcher && update-rc.d idle_watcher defaults && service idle_watcher start && /start.sh '
14 replies
Notification When Pod Is Deployed
I thought about it and the cronjob is the way to go. Having a separate server is too large of a security liability. The poor user experience of getting booted is only there for people who don't follow the recs, so I'm okay with that.
50 replies
Notification When Pod Is Deployed
Yeah, I guess that could work instead of periodically checking. That still requires me to put up a server which I'd have to separately manage, but I can just byte the bullet if need be....
I'll have to do some thinking on which exactly is the right call. Thanks
50 replies
Notification When Pod Is Deployed
Yes, that's the whole issue of it. I can communicate and I can set up interfaces but people can (and prob will) still set up pods without it, and what I'm looking for is an enforcement mechanism.
The hacky way around it is setting up a cronjob on a server which periodically checks the pods deployed, which seems like is what I'll need to do. It's just a pain to do so and I wish runpod had better admin infrastructure in place
50 replies