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

[chore] gitignore /bin entry #970

Merged
merged 1 commit into from
Nov 6, 2022
Merged

Conversation

lzap
Copy link
Contributor

@lzap lzap commented Nov 6, 2022

Hey,

I like to keep GOBIN in the project directories so when switching Go versions (my main Go is still 1.18 because our slower infra ops team) binaries do not fight between projects.

Just for the record, this tool https://direnv.net allows switching Go versions easily:

[lzap@nuc gotosocial]$ cat .envrc 
GOVER=1.19.3
export GOROOT="$(go$GOVER env GOROOT)"
PATH_add "$(go$GOVER env GOROOT)/bin"
export GOBIN="$(pwd)/bin"
PATH_add "$(pwd)/bin"

Thanks!

@tsmethurst
Copy link
Contributor

Thanks!

@tsmethurst tsmethurst merged commit f800970 into superseriousbusiness:main Nov 6, 2022
@lzap lzap deleted the gitignore branch November 6, 2022 10:45
@lzap
Copy link
Contributor Author

lzap commented Nov 6, 2022

Well I thank you!

I am installing right now, I am hoping for a small and easy to maintain instance. If it goes well, I will write a SELinux policy (I am not too much into containers :-) and share this work of course :-)

If you have any hints for me where the binary might read and write, let me know. I am assuming:

  • Postgres
  • SQLite database file/directory
  • Main data directory (files)
  • HTTP(s) in and out
  • S3
  • Temporary files maybe?

That should be pretty small policy indeed.

@tsmethurst
Copy link
Contributor

Off the top of my head, I think your list is pretty complete 🤔 If you wanna make an issue for SELinux policy we can try to enumerate there what permissions would be necessary

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.

2 participants