Setup a volume for the vpn file so it doesn't disappear when the container starts
Add an entrypoint script that starts the vpn if already setup (maybe remember the state by writing it to a file?)
Kill switch implementation?
- Setup a volume for the vpn file so it doesn't disappear when the container starts
- Add an entrypoint script that starts the vpn if already setup (maybe remember the state by writing it to a file?)
- Kill switch implementation?
Not to make you more work but maybe it'd be interesting to look at "kill switch" implementations in general, and what would that look like for different kinds of Co-op Cloud deployments?
Kinda like a backup-bot-two implementation, a seperate thing but with some permissions to do stuff that you configure. Don't feel obliged to go down this rabbit hole. Whatever you do here, we're sure to learn from it.
> Kill switch implementation?
Not to make you more work but maybe it'd be interesting to look at "kill switch" implementations in general, and what would that look like for different kinds of Co-op Cloud deployments?
Kinda like a `backup-bot-two` implementation, a seperate thing but with some permissions to do stuff that you configure. Don't feel obliged to go down this rabbit hole. Whatever you do here, we're sure to learn from it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Not to make you more work but maybe it'd be interesting to look at "kill switch" implementations in general, and what would that look like for different kinds of Co-op Cloud deployments?
Kinda like a
backup-bot-twoimplementation, a seperate thing but with some permissions to do stuff that you configure. Don't feel obliged to go down this rabbit hole. Whatever you do here, we're sure to learn from it.