I've been using it to generate Docx/PDF from my markdown.
Just started to explore means to customize (with tex template). Recent updated obsidian plugin requires explicitly configuring pandoc with latex which started the rabbithole customizing experiment :)
I use different browser with multiple profiles, so i've a clean history and separation of work. Though i love some basic features like searching tabs, it was very limiting wrt privacy/blocking.
I've tried my best to adopt, the major issue was default color management and couldn't disable it. It keeps changing my display (brightens). I wish a browser releases a feature to consume less memory!
Versioning, feature toggle and rollback - automated and implemented at different level based on the system. It could be an env configuration, or db field or down migration scripts or deploying last working version.
Apart from building one myself, I've noticed many organizations building config-management systems internally since they need to manage secrets/config with features like versioning, rollbacks, etc, on their cloud.
Thought AWS and GCP has KMS, it doesn't fit the orgs with multiple service and environments requirement. I will be adding multi cloud support and critical features of secrets management workflow. I would love to hear your thoughts.
I have a similar setup of Nginx proxy, Backends are Go binaries (without Docker) and Postgres. If it's for a pet project the free tier on GCP suffices.
If it's for a side project, i would think about resiliency and lasting for long time once there's a need for it. This's also contributed by the stack or how you setup infra. So don't bother initially.
You can pick a framework if you're comfortable with mix of frontend and backend (rails, django etc)
If you are more on backend, pick say react in frontend and your choice of language in backend and write monolith. Have a database if needed. Avoid cache completely (You don't need to scale or make it performant). Infact you can use file based db (eg: bolt) and add Pg/Mongo/Sql later.
My usual setup is,
1. Go for backend, react frontend
2. Deployed backend in free-tier GCP VM
3. Deployed frontend in Netlify/Heroku
4. Use free pg database in Heroku
Avoid self provisioning as much as possible if you don't need the control.
If it's for Indiehacker project, would suggest to not build it right away, use nocode platform or template to setup landing page, validate and do things.
Have done few OSS, Go wrapper on top of gcloud client to do the tedious job of searching across whole infra for set of Vms (DBs, Kafka clusters, or any components etc) and login with tmux. Useful for my workflow.
Have done other dev projects for improving my productivity (eg. Infra setup, Automation etc) which all aligns with fact that i'm the first user and not worried about its success.
Even-though not focusing on marketing for the same, i wish more people use it and can extend it for value add then complex featurewise.