14 karma · joined August 8, 2021
Would be interesting to know what issues you faced considering monorepo and what pushed to have multiple repos.
Still, I have recently hit a major issue with the fact that GIT (and other common version control sw) don't have per-directory ACL.
Has anyone dealt with this issue? Which VCS / configuration have you adopted?
Yes, we use a container for dev environment so that we can share the same env across all the team. If it's decided that we need 1 more tool in our toolbox, the script that generates the container is updated (the script is version controlled in the repo too), the CI/CD generates a new container version, all the devs can now use the same NEW environment.
We actually use the container as image for (remote) virtual machines, so we don't really compose multiple containers.
The container has all the tools (for several languages) that we use as a team.
IDEs and debuggers can connect through ssh.
> post-development workflow do you ever use separate containers for build and test?
We build different flavors of the final packaged application, for example:
- production flavor: uses a minimal, nonroot container base image (see: https://github.com/GoogleContainerTools/distroless)
- debug flavor: includes few extra debug tools inside the container
It definitely takes extra effort to remove the unnecessary and identify what actually brings value in the design, and in the content.
(together with a small change I made to Hugo to strip the '.html' extension from the page names)
Actually re-published today after spending way too much time tweaking with minimalist design. (any other perfectionist here?)
Will host technical writing and travel/digital-nomad reflections.
Made with Hugo and a custom theme.
Regarding just using raw postgres sockets, the CONS is that it gets harder to code the client in javascript (I don't think webassembly can handle sockets yet?)
Security-wise, it can actually be done (see how firebase handles security) but you need a way (API layer? StoredProcedures?) to verity auth tokens (like JWT) sent from the clients
Nevertheless, cool idea! wish you the best!