-
Notifications
You must be signed in to change notification settings - Fork 133
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
Deploying to redis via an ssh tunnel #108
Comments
Seems to me that having this as an option for ember-(cli-)deploy-redis makes sense, but I'd like to hear @LevelbossMike's input. |
As we migrate to ember-cli-deploy(-redis) we will need to resolve this exact same problem because our production Redis servers are limited similarly to @mnutt 's environment. I'm in favor of the last bullet point of supporting opening a tunnel for the duration of the deploy and merging into ember-deploy-redis. |
this seems like a useful addition to ember-deploy-redis. And like a use-case that should be supported by the plugin because it's annoying for everyone to set this up themselves and there are definitely a lot of people that need it. |
👍 for this. This is exactly what Im looking for. |
👍 from us, too. To our interests, this is indeed relevant. |
Since this is Redis specific, the issue is now here . @LevelbossMike think it's OK to close this issue and track with the ember-deploy-redis issue? |
yup. closing in favor of LevelbossMike/ember-deploy-redis#4 |
My team has a deployment process very similar to ember-cli-deploy's default, but our redis server isn't directly accessible from our local machines due to firewall rules. The options I see are:
The extra options could look like:
(I opened the issue here since I know there are a lot of big changes coming to the plugin system, but I can move it to the ember-deploy-s3 repo if that is a better place for it.)
The text was updated successfully, but these errors were encountered: