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

Add notes in settings that require a restart #1492

Closed
2 of 3 tasks
geekgonecrazy opened this issue Nov 25, 2015 · 16 comments
Closed
2 of 3 tasks

Add notes in settings that require a restart #1492

geekgonecrazy opened this issue Nov 25, 2015 · 16 comments
Assignees
Milestone

Comments

@geekgonecrazy
Copy link
Contributor

geekgonecrazy commented Nov 25, 2015

Many settings require restarting rocket.chat. We need to make note of these changes.

@RocketChat/core do we have others? This would probably make a good set of tasks for someone new that wants to contribute. I know there are more. :)

@marceloschmidt
Copy link
Member

In this specific case (accepted media types), are you sure a server restart is required? Isn't just the client that needs to refresh the browser?

@geekgonecrazy
Copy link
Contributor Author

@marceloschmidt i'm not completely sure. It seemed to be with this and also #1304 that a server restart was all that solved it.

@marceloschmidt
Copy link
Member

I'll give it a try later on, but as far as I remember, the accepted media types is only used for building a <input type="file" accept="{{accepted_media_types}}"> tag. So if the client re-renders it, it would correctly fetch the information... but that's my best guess, I'll give it proper testing later on.

@geekgonecrazy
Copy link
Contributor Author

@marceloschmidt that sounds right. I think there are a few others like this, otherwise I wouldn't have bothered to create a list. Now I just have to remember the other ones lol

@engelgabriel
Copy link
Member

If we find settings that require a restart, let's try to fix this before making a note about it. I don't think any settings should require a restart.

@sampaiodiego
Copy link
Member

Settings related to MAIL_URL seems needs a restart (confirmed, it needs)

@engelgabriel
Copy link
Member

OK, but it can and should be fixed.

@sampaiodiego
Copy link
Member

needs a real test.. but looking at source code seems like push notification settings needs a restart too

marceloschmidt added a commit that referenced this issue Dec 30, 2015
No need to reload server for SMTP settings to take effect;
Closes #1246
Checks SMTP Settings in #1492
@kreuzebek kreuzebek mentioned this issue Jan 6, 2016
@mitar
Copy link
Contributor

mitar commented Jan 15, 2016

BTW, you can make server-side automatically restart itself by calling process.exit(0) on the server side.

@marceloschmidt
Copy link
Member

As per #3020 it looks like changing Storage Type needs a restart as well

@sampaiodiego
Copy link
Member

Just the avatar storage type @marceloschmidt ;)
the file upload storage type doesn't need a restart

@Rohlik
Copy link
Contributor

Rohlik commented Mar 24, 2017

I think this is solved, so we can close this.

@geekgonecrazy
Copy link
Contributor Author

@Rohlik I believe so. I'll go ahead and close @marceloschmidt / @sampaiodiego let me know if closing in error :)

@sampaiodiego
Copy link
Member

We still need a restart for Push notification settings.

@geekgonecrazy
Copy link
Contributor Author

@sampaiodiego ah right... we don't have a note there telling them a reboot is needed. Re-opening..

@geekgonecrazy geekgonecrazy reopened this Mar 24, 2017
@robertwessen
Copy link

any update here? spent waaaayyy too long trying to figure out what was wrong with my push settings, since i could toggle them and things were still broken. Finally out of desperation tried a reboot and then settings worked? Then searched and found this issue... @sampaiodiego @geekgonecrazy

@sampaiodiego sampaiodiego added this to the 0.69.0 milestone Aug 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants