Skip to content

Conversation

@CoderMiguel
Copy link

I wanted to dynamically update the version of Tailscale to the latest available so I wrote a refactor to handle that and still allow a configured version to be used. I added a TODO: to log the discrepancy in versions similar to other buildpacks I have used, but wanted to start a conversation before building that logic.

Example:

###### WARNING:
remote: 
remote:        There is a more recent Ruby version available for you to use:
remote:        
remote:        3.2.9
remote:        
remote:        The latest version will include security and bug fixes. We always recommend
remote:        running the latest version of your minor release.

(tailscaled -verbose ${TAILSCALED_VERBOSE:--1} --tun=userspace-networking --socks5-server=localhost:1055 > /dev/null 2>&1 &)
(tailscaled -verbose ${TAILSCALED_VERBOSE:--1} --tun=userspace-networking --socks5-server=localhost:1055 > /dev/null 2>&1 &)
tailscale up \
--authkey="${TAILSCALE_AUTH_KEY}?preauthorized=true&ephemeral=true" \
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is covered in my other PR

Comment on lines -48 to +52
--timeout=15s \
${TAILSCALE_ADDITIONAL_ARGS:---timeout=15s}
${TAILSCALE_ADDITIONAL_ARGS:---accept-routes --timeout=15s}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is covered in my other PR

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

Successfully merging this pull request may close these issues.

2 participants