I have a similar setup, I use Caprover as a nicer way to manage docker. You can build whatever you want into the dockerfile then just map the user directory to a local one and port forward where needed.
If you want to run a web app through a domain with SSL then it's trivial to setup a nginx proxy container.
It takes minutes to spin up a new dev environment with everything setup out of the box including environment variables and access tokens.
A few months ago a wrote about how I solve this problem (https://www.viadog.com/replacing-environment-variables-aws-s...) and it works nicely for a small team with a small number of projects but this looks like a very nice solution when starting to scale a little bigger.
Hi everyone, I'd like to share Viadog Subscriptions which is my first product. It's targetted towards Shopify/ReCharge shop owners and helps to both increase revenue through upselling and reduce churn through gifting.
I'm happy to answer any questions and also open to feedback.
This would be simple for the user to execute but it would very quickly be spotted by the operator as it's all from a single originating MSISDN.
Spreading the load over many users like your latter example would be a lot harder to spot, as would spamming through multiple SMS providers as you're diluting it (but it might also get picked up by the provider e.g. Twilio, MessageBird etc).
My point was that most spam originates from people with SS7 access and not SIM cards. It can also come through low cost SMS providers but is short lived as it's blocked the moment it's discovered or there's a complaint.
Bulk SMS spam would most likely come from someone with direct signalling access and not from individual SIM cards which would be trivial to detect and block by the operator.
I just did a write up about how we use a secrets manager to load our environments allowing an easy centralised management across multiple projects/envs.
I do this too and it's so easy to manage all your local and remote environments from one place, I go one step further and push them to my environment variables too rather than use a dotfile
You should take a look at Amplify (https://aws.amazon.com/amplify/), it will make the whole process considerably less painful, allow you to easily access AppSync (graphql) and Lambda with your code all in one place, then also trigger rebuilds on git commits.
Hi, have you thought about hosting for this yet? I've got a similar site which I originally tried on AWS Amplify but it got too big for the artifact size limit so I opted for S3/Cloudflare instead however build times are slow and more of a manual process currently.
If you want to run a web app through a domain with SSL then it's trivial to setup a nginx proxy container.
It takes minutes to spin up a new dev environment with everything setup out of the box including environment variables and access tokens.