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

Fix sidekiq.service for use as user service #6191

Merged
merged 1 commit into from Feb 8, 2024

Conversation

Yegorov
Copy link
Contributor

@Yegorov Yegorov commented Feb 8, 2024

When rebooting the system, the user service was not launched automatically.

@mperham
Copy link
Collaborator

mperham commented Feb 8, 2024

Please explain why.

@Yegorov
Copy link
Contributor Author

Yegorov commented Feb 8, 2024

Because, for user service only available default.target
I had a similar problem as here

Also see: systemd/systemd#2690

@mperham
Copy link
Collaborator

mperham commented Feb 8, 2024

Sidekiq is not typically deployed as a user-specific service. That .service file works for most Sidekiq users but if you deploy it differently, you must expect to adjust the .service file.

@Yegorov
Copy link
Contributor Author

Yegorov commented Feb 8, 2024

I think, this case must be documented in the template so that other users are not surprised by this behavior
Besides, here it is already indicated how to make user service #4938

@mperham
Copy link
Collaborator

mperham commented Feb 8, 2024

We can document it as a comment but I don't think the actual configuration should change.

@mperham mperham merged commit 1df02c8 into sidekiq:main Feb 8, 2024
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

2 participants