Possible to give read/write access to the group when creating the config.json? #65

New Issue

Ghost · 2020-09-29T20:01:42Z

Ghost commented

2020-09-29 20:01:42 +00:00

Right now, I have a problem in my system: each time someone start the server, it will recreate the file config.json with the following credentials:

-rw------- 1 <user> <group>  804 Sep 29 19:52 config.json

So when someone else tries to restart the server it will fail because it cannot read the config.json file.

Is it possible to change the behavior to give access to the whole group?

Right now, I have a problem in my system: each time someone start the server, it will recreate the file config.json with the following credentials: ``` -rw------- 1 <user> <group> 804 Sep 29 19:52 config.json ``` So when someone else tries to restart the server it will fail because it cannot read the config.json file. Is it possible to change the behavior to give access to the whole group?

coolaj86 commented

2020-09-30 02:20:15 +00:00

Checkout https://webinstall.dev/serviceman

That's the easiest way to use systemd so that the service is owned by a specific user/group rather than changing hands with each user.

Checkout https://webinstall.dev/serviceman That's the easiest way to use `systemd` so that the service is owned by a specific user/group rather than changing hands with each user.

coolaj86 commented

2020-09-30 02:22:30 +00:00

For example:

pushd ./my-node-app/

sudo env PATH="$PATH" \
    serviceman add --system --cap-net-bind \
    npx nodemon ./server.js

pushd ./my-node-app/

sudo env PATH="$PATH" \
    serviceman add --system --cap-net-bind \
    npm start

For example: ```bash pushd ./my-node-app/ sudo env PATH="$PATH" \ serviceman add --system --cap-net-bind \ npx nodemon ./server.js ``` ```bash pushd ./my-node-app/ sudo env PATH="$PATH" \ serviceman add --system --cap-net-bind \ npm start ```

Ghost commented

2020-09-30 20:45:32 +00:00

Sorry man. Actually I think that I was responsible for the config.json being written with wrong permissions. I thought it was part of greenlock process.

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: root/greenlock-express.js#65