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

SSL configuration creation #31

Merged
merged 4 commits into from
Sep 24, 2016
Merged

SSL configuration creation #31

merged 4 commits into from
Sep 24, 2016

Conversation

Pe46dro
Copy link
Collaborator

@Pe46dro Pe46dro commented Sep 8, 2016

PR as requested #28

Now the file generation will be made after domain variable definition and configuration will be tested with the correct name

Sorry for multiple commits but i made it from Github Web

Check if file exists after domain definition
Now test-new-config.sh should be able to enable the correct site
Now the test enable the configuration file created in activate-ssl.sh
@enoch85
Copy link
Member

enoch85 commented Sep 9, 2016

@ezraholm50 Please test this, doesn't seem right at first look. Thanks!

@Pe46dro Thanks for your PR!!

@@ -242,7 +245,7 @@ fi
# Check if $certfiles exists
if [ -d "$certfiles" ]; then
# Activate new config
bash /var/scripts/test-new-config.sh
bash /var/scripts/test-new-config.sh $domain.conf
Copy link
Member

Choose a reason for hiding this comment

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

Have you actually tested this?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

test-new-config.sh is a totally different script that tests the configuration and has nothing to do with the domain name. @Pe46dro Please explain this fix.

@enoch85
Copy link
Member

enoch85 commented Sep 24, 2016

I just checked this a little but more and understands the fix, not tested though.

Lets's merge this anyway and see what response we get from other users.

👍 From me.

@enoch85 enoch85 merged commit 01e87a0 into nextcloud:master Sep 24, 2016
@Pe46dro
Copy link
Collaborator Author

Pe46dro commented Sep 24, 2016

Essentially before my change when you run the lets-encrypt/activate-ssl.sh file a .conf file was generated (only .conf, no name, because the $domain used in $ssl_conf definition was defined before FQDN input ) and when you run the test-new-config.sh you always try to enable the nextcloud_ssl_domain.conf configuration.

WaaromZoMoeilijk pushed a commit that referenced this pull request Feb 6, 2017
@RKlarmann RKlarmann mentioned this pull request Apr 8, 2020
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.

None yet

3 participants