Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback from first run. #69

Open
stereosteve opened this issue Nov 21, 2024 · 1 comment
Open

Feedback from first run. #69

stereosteve opened this issue Nov 21, 2024 · 1 comment

Comments

@stereosteve
Copy link

stereosteve commented Nov 21, 2024

Hello - thanks for making this project. Like the simplicity and it mostly worked as advertised. Here are some gotchas I encountered from first run.

I think it'd make sense to add some notes to the documentation so people are more likely to have a good first-run experience:

  • Server needs to be ubuntu
  • sidekick init disables root ssh. You must use ssh sidekick@ henceforth.
  • container should expose port for the sake of health checks since health checks happen from host machine (outside of docker network)
  • server should have an /up endpoint also for health checks.

For zero-downtime deploys a few issues:

  • The HEALTHCHECK CMD from this example dockerfile caused several seconds of downtime during deploy.
  • After removing that HEALTHCHECK CMD... there would still be a few requests which timed out / didn't get a response during a deploy. I suspect this has to do with how nodes are added / removed from Traefik. This is probably why Kamal wrote a custom kamal-proxy... and I wonder if in the long run that might be a good option as it looks pretty nice.
@leomorpho
Copy link

It would be nice to have a quick way to delete any previous setup with sidekick and start from a blank slate for a server IP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants