Join devRant
Do all the things like
				++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
				Sign Up
			Pipeless API
 
				From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
				Learn More
			Search - "github push to prod"
		- 
				    					
					
					TL;DR: When picking vendors to outsource work to, vet them really well.
 
 Backstory:
 Got a large redesign project that involves rebuilding a website's main navigation (accessibility reasons).
 Project is too big just for our dev team to handle with our workload so we got to bring a 3rd party vendor to help us. We do this often so no big deal.
 But, this time the twist was Senior Management already had retained hours with a dev shop so they want us to use them for project. Okay...
 
 It begins:
 Have our scope / discovery meeting about the changes and our expected DevOps workflow.
 
 Devs work Local and push changes to our Github, that kicks off the build and we test on Dev, then it goes to Staging for more testing & PM review. Once ready we can push to prod, or whenever needed. All is agreed, everyone was happy.
 
 Emailed the vendors' project manager to ask for their devs Github accounts so we can add them to the project. Got no reply for 3 days.
 
 4th day, I get back "Who sets up the Github accounts?"
 
 fuck me. they've never used Github before but in our scope meeting 4 days ago you said Github was fine...??
 
 Whatever, fuck it. I'll make the accounts and add them.
 
 Added 4 devs to the repo and setup new branch. 40min later get an email that they can't setup dev environment now, the dev doesn't know how to setup our CMS locally, "not working for some reason."
 
 So, they ask for permission to develop on our STAGING server.. "because it's already setup"... they want to actively dev on our staging where we get PM/Senior Management approvals?
 
 We have dev, staging, production instances and you want to dev in staging, not dev?... nay nay good sir.
 
 This is whom senior management wants us to use, already paid for via retainer no less. They are a major dev shop and they're useless...
 
 😢😭
 
 Cant wait for today's progress checkup meeting. 😐😐
 
 /rant1
- 
				    					
					
					Question for NextJS/JS developers: I had a "it works on my machine" argument with a frontend dev. We were both hired separately, him doing frontend/backend dev and me doing the AWS dev to prod ci/cd stuff. The setup is that once he pushed code, my Github Actions setup will compile the nextjs app, and push it to dev or prod depending on which branch he pushes it to. His nextjs app was unable to read the .env file on the server but the python/fastapi one can. He kept pointing the finger at me so I had to look it up. Apparently, env values are inlined at build time and he didn't know. What the philosophy behind this design? If there's any changes to env file, you'll have to go to the process of rebuilding.10

