Ranter
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
Comments
-
We always do our releases during working hours but we don't have any downtime, normally the old and new version run in parallell for a few seconds, the old one is removed from the load balancer once the new one is completely up and running.
-
olezhka25727y@ItsNotMyFault ah good strategy! I only use one front end for active users. Have another dedicated solely for indexing of content
-
Deployment should be seamless whenever possible (no down time) and also in work hours in case of a disastrous bug
-
LMagnus20577yYeah we do. Depends on the application/ service it is on whether there is any downtime. If it's anything that requires significant downtime we'll do it over the weekend when the majority of users aren't in the office.
Much prefer to deploy in working hours as there is much more support available if there are issues. Also means issues are usually dealt with on work's time and not my own. -
olezhka25727y@LynxMagnus @ClemFrieckie Good to know, thanks guys! It also lets me gather immediate feedback, too, as there are so many ways / configurations people could decide to use the software with - it only ever becomes clear then if there's some obscure but apparently quite widely userd scenario I did not forsee
-
olezhka25727y@OverCoder Of course. But if you have a slight downtime it helps to target least active hours, early in the morning for instance
-
first 6 years od my php dev career was no version control, testing by special GET switches that redirected the flow to what i'm devving, everything live on prod servers.
at first it was horribly stressful, then it became refreshingly andrenaline, then it became just normal.
but it seems you're asking about something else, something that's not outright the worst practices ever™ -
olezhka25727y@Midnigh-shcode it was more just to get a finger on a general pulse on what peoples' thoughts are on this topic, like yay or nay. :)
-
I have the luxury of being 7 hours behind my users - I love in Israel but all our clients are American (our software is US only) - so I can deploy as slowly as I like, check that it works, etc.
Related Rants
Does anyone of you fellow devs ever pushes to production during working hours?
I have the luxury to do so and at first was uncomfortable, as this of course takes the system offline for a few seconds, and next web requests from a user are painful due to cold start of web server (and we have 40-100 active users at any given time)...
...but you know what? They all complain SharePoint is slow (it is) anyway, so. I do it.
Sometimes it fucking fails, so I do have all of the historic deployments handy, ready to revert. :)
undefined
no standards
wild
deployments
savage