why some files are hidden? #37

New issue

Closed

opened 2025-12-28 18:08:11 +00:00 by sami · 5 comments

sami commented

2025-12-28 18:08:11 +00:00

Owner

Originally created by @532910 on GitHub (Apr 6, 2022).

.dockerignore, .gitignore, .git, .editorconfig are hidden, but they are not a part of this project, just a helpers for git and others.

And the question is: why .env, .services and .basic_services start with dot?

Originally created by @532910 on GitHub (Apr 6, 2022). `.dockerignore`, `.gitignore`, `.git`, `.editorconfig` are hidden, but they are not a part of this project, just a helpers for git and others. And the question is: why `.env`, `.services` and `.basic_services` start with dot?

sami

2025-12-28 18:08:11 +00:00

closed this issue
added the
U4

I3

question

S4
labels

sami commented

2025-12-28 18:08:12 +00:00

Author

Owner

@alexvanin commented on GitHub (Apr 14, 2022):

¯\(ツ)/¯
I don't think there is a particular reason for that. Moreover other dotenv files such as service/ir/.ir.env and service/storage/.storage.env are also hidden.
Are there any issues with it, though?

@alexvanin commented on GitHub (Apr 14, 2022): ¯\\_(ツ)_/¯ I don't think there is a particular reason for that. Moreover other dotenv files such as `service/ir/.ir.env` and `service/storage/.storage.env` are also hidden. Are there any issues with it, though?

sami commented

2025-12-28 18:08:12 +00:00

Author

Owner

@532910 commented on GitHub (Apr 14, 2022):

service/ir/.ir.env and service/storage/.storage.env also should be unhidden

@532910 commented on GitHub (Apr 14, 2022): `service/ir/.ir.env` and `service/storage/.storage.env` also should be unhidden

sami commented

2025-12-28 18:08:12 +00:00

Author

Owner

@alexvanin commented on GitHub (Apr 14, 2022):

I don't mind having those files unhidden. Should not affect developer's workflow, however it might require some changes in integration tests. @aprasolova can you check that?

@alexvanin commented on GitHub (Apr 14, 2022): I don't mind having those files unhidden. Should not affect developer's workflow, however it might require some changes in integration tests. @aprasolova can you check that?

sami commented

2025-12-28 18:08:12 +00:00

Author

Owner

@aprasolova commented on GitHub (Apr 14, 2022):

In integration tests, we only use .int_test.env. It's trivial to support the "unhiding" of the files.
@EliChin

@aprasolova commented on GitHub (Apr 14, 2022): In integration tests, we only use [.int_test.env](https://github.com/nspcc-dev/neofs-dev-env/blob/master/.int_test.env). It's trivial to support the "unhiding" of the files. @EliChin

sami commented

2025-12-28 18:08:12 +00:00

Author

Owner

@roman-khimov commented on GitHub (Dec 28, 2024):

I think this property will make it easier to reintegrate dev-env into the main node repository. WONTFIX here.

@roman-khimov commented on GitHub (Dec 28, 2024): I think this property will make it easier to reintegrate dev-env into the main node repository. WONTFIX here.