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

How can we give access to user in rollout #36

Open
ghost opened this issue Dec 1, 2015 · 8 comments
Open

How can we give access to user in rollout #36

ghost opened this issue Dec 1, 2015 · 8 comments

Comments

@ghost
Copy link

ghost commented Dec 1, 2015

I am using rollout as a configuration manager.

I am using nginx as webserver and want to give read only access to nginx directory to a user.

How can I do that?

Please help me with this.

Thanks

@dparrish
Copy link
Owner

dparrish commented Dec 1, 2015

This is a very broad question, I'm not sure exactly what you're asking here.

  • If you want to give read only access to the directory from the shell, use
    the normal unix chown/chmod tools, that's nothing to do with nginx or
    rollout.
  • If you want to give read only access over HTTP (through nginx) then
    you'll need to configure HTTP authentication in nginx (
    https://www.howtoforge.com/basic-http-authentication-with-nginx). Keep in
    mind that Rollout doesn't support HTTP authentication for it's HTTP
    requests, I've always relied on firewalls or port filtering for that.
  • Rollout itself doesn't have any idea of authentication or users.

On Tue, Dec 1, 2015 at 3:34 PM, rishii2129 [email protected] wrote:

I am using rollout as a configuration manager.

I am using nginx as webserver and want to give read only access to nginx
directory to a user.

How can I do that?

Please help me with this.

Thanks


Reply to this email directly or view it on GitHub
#36.

@ghost
Copy link
Author

ghost commented Dec 1, 2015

Thank you for the reply.

It's my pleasure to have a conversation with you. I have configured the nginx and managing everything via rollout.

If you need then I can give you my configured codes for the same.

I have attached the sample for the reference.

Nginx.txt

Thanks!

@dparrish
Copy link
Owner

dparrish commented Dec 1, 2015

I still don't know what you mean by "read-only access to any specific user".

Do you mean access from the command line or by HTTP?

On Tue, Dec 1, 2015 at 4:41 PM, rishii2129 [email protected] wrote:

Thank you for the reply.

It's my pleasure to have a conversation with you. I have configured the
nginx and managing everything via rollout.

If you need then I can give you my configured codes for the same.

I have attached the sample for the reference.

Nginx.txt https://github.com/dparrish/rollout/files/48118/Nginx.txt

Thanks!


Reply to this email directly or view it on GitHub
#36 (comment).

@ghost
Copy link
Author

ghost commented Dec 1, 2015

access via command line over linux server

@dparrish
Copy link
Owner

dparrish commented Dec 1, 2015

You can add a dir_check block

dir_check => [
[ '/app/nginx', 0755, 'www-data', 'www-data' ],
]

That ensures that the /app/nginx directory exists, and is owned by the
www-data user and group. The permissions (0755) allow any user to read the
directory.

On Tue, Dec 1, 2015 at 5:54 PM, rishii2129 [email protected] wrote:

access via command line over linux server


Reply to this email directly or view it on GitHub
#36 (comment).

@AlienResidents
Copy link
Contributor

Hi,

The dir_check in your configuration, and what dparrish mentioned will give
read-only access to all users (except root, and www-data) to the
'/app/nginx' directory only. Anything further down the directory tree is
not going to be guaranteed to have read-only permissions based on your
configuration. Do you want to ensure recursive read-only permissions for
'/app/nginx'?

Chris-

On Tue, Dec 1, 2015 at 6:25 PM, David Parrish [email protected]
wrote:

You can add a dir_check block

dir_check => [
[ '/app/nginx', 0755, 'www-data', 'www-data' ],
]

That ensures that the /app/nginx directory exists, and is owned by the
www-data user and group. The permissions (0755) allow any user to read the
directory.

On Tue, Dec 1, 2015 at 5:54 PM, rishii2129 [email protected]
wrote:

access via command line over linux server


Reply to this email directly or view it on GitHub
#36 (comment).


Reply to this email directly or view it on GitHub
#36 (comment).

@ghost
Copy link
Author

ghost commented Dec 2, 2015

Hi Chris,

Thanks for you reply!!

I have heard a lot of about you. It's my please to have a conversation with you.

I can't tell you how much I am happy while talking to you.

Actually my requirement is to give read only access on all nginx servers in my infrastructure to a user.

We are using few static servers, in which we are running nginx.
User wants read only access to all directory used by nginx. Do I need to add user in www-data group in rollout?

If you want to see the configuration, then I can give you all codes for better understanding.

Also I am getting one error in rollout as attached below:

Rollout error.txt

what does this means and how can I resolve this?

Thanks

@AlienResidents
Copy link
Contributor

Hi,

Those errors in the file 'Rollout.error.txt' aren't rollout related.

Chris-

On Wed, Dec 2, 2015 at 12:54 PM, rishii2129 [email protected]
wrote:

Hi Chris,

Thanks for you reply!!

I have heard a lot of about you. It's my please to have a conversation
with you.

I can't tell you how much I am happy while talking to you.

Actually my requirement is to give read only access on all nginx servers
in my infrastructure to a user.

We are using few static servers, in which we are running nginx.
User wants read only access to all directory used by nginx. Do I need to
add user in www-data group in rollout?

If you want to see the configuration, then I can give you all codes for
better understanding.

Also I am getting one error in rollout as attached below:

Rollout error.txt
https://github.com/dparrish/rollout/files/49285/Rollout.error.txt

what does this means and how can I resolve this?

Thanks


Reply to this email directly or view it on GitHub
#36 (comment).

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

No branches or pull requests

2 participants