Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I also think a multi file modular setup is the way to go. I do this in tandem with use-package statements and it works well and is relatively easy to troubleshoot. You’re welcome to see what might be useful to you from my config: https://github.com/mclear-tools/dotemacs
I have everything in a literate configuration written in Org Mode, I also use straight.el so I don't make any use of use-package statements
Same here using “proper” modules to avoid having to think about load order, with host-specific configuration. Since I live in Emacs when I’m coding anyway, any loss in startup time is made up for by it being easy to manage and reason about. Since it’s easier to show rather than tell - https://github.com/brett-lempereur/.emacs.d
module custom) init.el file which daisy chains to config.el
Between org babel SQL and ob-restclient literate integration testing and devops have become a (small) part of my team's dev-QA loop. For some things, it's turned out to be indispensable. If you haven't used org-mode and restclient for API documentation yet... give it a whirl. Beautiful exports use read-the-org HTML export theme.
I keep meaning to explore using org-mode for this. At the moment I have a trivial init.el which loads a literate markdown file init.md.
You can check it out here. I'll gladly take advice on improving it!