| how does it work ? it is git integrated i assume...and do u export a Dockerfile or something to replicate the exact runtime ? my fundamental question is : how easy is it to go from writing code to production deployment ?
This has been the big issue with cloud dev. Take an example of Python flask with Pandas. There are problems depending on whether u used an alpine dev environment or debian. Now if i just take the code and try to deploy it on redhat...it goes all screwy. lots of the c library extensions start screwing up. Can i single click create a running docker environment with my running code EXACTLY like the code dev environment. Funnily enough, the only good one here is AWS Sagemaker - https://docs.aws.amazon.com/sagemaker/latest/dg/docker-conta... They do this for machine learning code. You can take your data and algorithms out of the ide and get a running docker container with all the build scripts and everything. second - ur pricing is off. part of the charm of a cloud dev environment is never turn it off. like shutting the lid of my macbook m1 and opening tomorrow morning. even the cursor is in the same place. There is zero incentive for me to shutdown a system and reopen tomorrow morning.
In that scenario, ur pricing for an 8 core 32 gb instance is 421 USD per month.
Comparitively a Google Cloud 8core 32 gb instance with 100 GB SSD is 212 USD. Sagemaker Python notebooks ml.t3.2xlarge are 0.399 USD per hour - about 288 USD per month. you will need to adjust pricing. replit pricing of 7$ hacker plan is cheaper than equivalent Sagemaker pricing (about 36$ per month) |
You can view Nimbus workspace as a linux machine that you have, but on the cloud. We built an internal Dockerfile-like IDL to replicate the exact dev environment every time when a new workspace is being created.
- We love Dockerfile, but we didn't directly build on top of it because there are more configurations we want to enable (such as on create/start/stop/delete lifecycle hooks, and personal/team configs).
- That being said, I can imagine exporting a Dockerfile can be feasible on Nimbus for the future (sufficient to replicate a new dev environment), but with certain Nimbus specific features missing there.
> it is git integrated i assume...
And yes, you are right! It's has git integration, and we are working on more tooling integrations right now to build better developer experiences (talking about all the source code management tool the team is using, credentials/env variable tools, etc)
> how easy is it to go from writing code to production deployment?
I'm totally with you. As an engineer myself, to me, only having code deployed on the production marks the completion of something, instead of just merging the code to the main branch. So it's important to have an efficient/stable way to move a piece of code to PR, to staging, and eventually to production.
As for Nimbus team, we don't solve this question as our main value prop, but we do facilitate that for sure, by
- making Nimbus a seamless part of engineers dev workflow (among all your task tracking, SCM, CI/CD tools)
- providing flexibly on setting up the dev environment (e.g. you can set it up in a way that is more consistent with the production setup, but still contain development-specific tools)
> Can i single click create a running docker environment with my running code EXACTLY like the code dev environment.
Not an expert of Sagemaker myself - do you mean auto-generating a Dockerfile based on your codebase? :-)