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

Alias or Addon Domains for V4 #23

Open
michacassola opened this Issue Jun 3, 2018 · 7 comments

Comments

2 participants
@michacassola

michacassola commented Jun 3, 2018

Please add the abbility to set or update the vhost domains with EE V4:

ee site create example.com --alias example.net --alias example.org
ee site update example.com --alias example.de --alias example.tld

Thanks!

Edits from @kirtangajjar:
The following command should add alias domains and get their SSL certs:
ee site update example.com --alias example.de --alias example.tld --ssl=le

@michacassola

This comment has been minimized.

michacassola commented Jul 14, 2018

Hey guys, @rahul286 @kirtangajjar @mbtamuli

thanks for the Beta 3 Release!

I have one question though as I have a use case that is also supported natively in wordpress:
ee site create example.com --alias example.net --alias example.org --wpsubdom --wpredis --le
Meaning a MU install is made with subdomains being the alias domains and they would also need to be included in the letsencrypt certificate.
And later one would want to add another domain like this:
ee site update example.com --alias example.net --alias example.org --alias example.info --le
adding another alias domain with LE and a MU subsite.

Will you please support this use case in the final v4?

(As a workaround with v3 I setup empty --php sites and change the location in the vHost file and also get the LE cartificate through the empty site ( ee site create example.com --php --le ). Maybe you could use this "Method" to stay flexible with the LE certificates in this kind of setup. Setting up a different for LE only NGINX container that points to the same location as the original domains htdocs folder.)

@rahul286 rahul286 added this to To do in v4.1 and Later via automation Aug 3, 2018

@michacassola

This comment has been minimized.

michacassola commented Aug 8, 2018

It makes me a bit sad @rahul286 that you removed the v4 release tag from this issue as I need this feature to use v4 as I don't know any workaround in v4.

@rahul286

This comment has been minimized.

Member

rahul286 commented Aug 9, 2018

Label release/4.x is deleted because we cleanup issue tracker to have only issues that are related to v4.

This issue is open because of its part of the scope. Although not 4.0 itself but probably 4.1 or later.

@michacassola

This comment has been minimized.

michacassola commented Aug 9, 2018

Thank you very much for clarifying @rahul286!

Once v4 is out, is there a possible workaround?

@michacassola

This comment has been minimized.

michacassola commented Aug 10, 2018

It would definitely have to be 4.1, it only makes sense in the "Development" release.

@michacassola

This comment has been minimized.

michacassola commented Nov 25, 2018

@rahul286 and @kirtangajjar

How do I do it manually best until we get the feature in v4.1?

Do I make a html site to get the LE autorenewal going and change the location parameter in the default.conf for the nginx-proxy service?
Or do I change the custom nginx.conf on the site level?
Or do I change the VIRTUAL_HOST parameter in the .env file of the site root, but then how do I rebuild the NGINX container with that environment variables?

Please help me so that it works and is also update resistant.

@mrrobot47 mrrobot47 added this to To Do in v4 Maintenance Releases via automation Nov 29, 2018

@mrrobot47 mrrobot47 removed this from To do in v4.1 and Later Nov 29, 2018

@michacassola

This comment has been minimized.

michacassola commented Nov 30, 2018

@kirtangajjar and @rahul286
Please move another earlier post of this to the feature-request repo and mark this one as duplicate or move this one and close the other. We should then change the title of the post so it includes all terminology in this direction.

@kirtangajjar kirtangajjar transferred this issue from EasyEngine/easyengine Nov 30, 2018

@michacassola michacassola changed the title from [Feature Request] Alias Domains for V4 to Alias or Addon Domains for V4 Nov 30, 2018

@mbtamuli mbtamuli added this to To Do in v4 Maintenance Releases via automation Dec 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment