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
-
Famous last words:
-"This change was so small, so there's no need for tests. I'll just deploy right away."9 -
Heroku allows you to deploy your webapp from Dropbox...
THIS IS NOT SOMETHING WE SHOULD ENCOURAGE!
5 -
No one dare deploy anything the week before Christmas - no fucking way I'm writing a hotfix under the Christmas tree again this year
-
Looks like I'ma deploy a new server tonight - a quadcore beast with 16GB of RAM. Let the funsies begin! 😁
39 -
Had to wake four people up at 2 am to fix a crashing service.
10/10 would deploy to production on Friday night again.
24 -
This is why you DONT deploy in a Friday!
Now can we all agree to stop disagreeing!
Ps: I love CommitStrip sometimes.
2 -
Dear Apple,
Fuck you.
Sincerely,
A bored developer forced to build and deploy with a virtualized OSX.10 -
Manager: "Pls deploy the changes ASAP."
Me: "Right away."
Me: *creates pull request*
... 5min later ...
GitHub: "Some checks haven't completed yet."
... 45min later ...
GitHub: "Some checks haven't completed yet."
Me: *looks into delay*
CircleCI: "Partial System Outage"
——
(╯°□°）╯︵ ┻━┻2 -
My first complete pipeline with Jenkins:
- push on gitlab
- build with maven
- test with junit
- deploy with Ansible
- integration test with Selenium
I love devops!6 -
Let's take bets on the root cause of the S3 outage!
I'm guessing a bad deploy of a sever-side Java application with a garbage collection problem.5 -
*production is down*
Ops: At 5pm? On a Friday? *checks deploy history* God! Who did the deploy
Dev: It was a small patch, a tiny patch. It shouldn't have....
Ops: Deploy on a Friday evening?
Colleague: I didn't think it would...
Ops (on the outside) : *takes a deep breath* Its okay Dev, we can fix this. Don't worry
Me(in my mind) : for fuck sakes! Are you fucking kidding me?*** **** *** god damn it! *****9 -
So I worked on getting a server ready for about 30 hours last week to be ready for a deploy on Monday Night (last night). Not only did I work on it for 30 hours, we had two other architects and a senior engineer working on it too. We got everything done Friday and it was ready to go with a simple cutover on Monday night.
The only thing left to do was deploy a link change Monday night on the existing landing page. My part was the backend servers and application that had the complicated SSO system and the other part was just a link to get to the SSO. I asked the person responsible for deploying the landing page's link if he was ready about a dozen times. He kept saying he was deploying X (the code name for the project deploy) and that is all he was doing.
Now jump to that night. They have decided that a single landing page wasn't enough and they were going to deploy a full CMS. Well no one knew what the hell was going on and they didn't realize that the landing page was hosted externally on another host. After arguing for two hours they delayed the deployment for multiple days. 24 hours later they are still trying to figure out the CMS on a host.
30 hours and four senior engineer's time wasted to get everything done for the deadline all to be canceled because of on jackass's lack of planning. WTF
2 -
"Read-only Friday" rule: On Fridays, you don't deploy new versions, don't merge code into production, don't update databases, and a lot of others "DON'Ts"4
-
My boss is making me deploy a major change what hasn't had proper testing yet on the day I leave for 2 weeks. Save me someone.13
-
I'm gonna deploy today. On Friday. On my last day of work.
MyCompany, are you sure that you want to end short-time employments on Fridays?1 -
Me: “I’ve done Kubernetes before what could possibly go wro-“
(cni0 breaks IPv4 routing serverside by containerd)
Me:
1 -
you might think that windows updates are painful but this piece of shit has been like this for an hour JUST LET ME FUCKING DEPLOY
12 -
Accidently deleted user table on production database and some backups where broken. Had to deploy a 4 days old backup...6
-
Valve deployed a CS:GO update this Friday, guess what. It had quite a few bugs.
Never deploy on a Friday, please.6 -
Unwritten devRant law #1:
if ($day === 'Friday') {
// add important words
$rant .= 'deploy';
$rant .= 'not';
}
print $rant;15 -
That paranoia when you deploy for production and you keep checking if it isn't down every 10 minutes.2
-
To all my fellow devs.
Do NOT deploy this weekend unless you want to debug in your parent's house in your old bedroom at midnight 😅4 -
Wanted to deploy my local files to remote server using rsync.
Used wrong syntax, replaced my local files with remote instead :(5 -
!rant
Those feelings you get when you deploy a large integration project that’s taken over a month to build and it just works 🤗2 -
Client asks for website and budget very low and wants a form with dB. Think WordPress site is a solution. Build site.
Deliver site.
Client's IT team unable to deploy on server. They blame me for bad "code".
I have to go to their office and help them deploy on local machine using WAMP.
2 days and 100s of calls later, website installed on test server. Works fine.
All is well1 -
The senior dev is mentoring our new recruit.
😨 I know, my face too.
When the newbie asked how to deploy, senior dev says, "Well, we copy and paste this folder from your local box to the server you need to deploy it on. Much better than that git shit, you have so much more control!"
😭4 -
It's currently 11:21 pm were I am, and I just finished working
I decided to deploy on a Friday
Those two things are related9 -
I've had two DevOps engineers ask me how I deploy new pipelines so quickly.
I show them how I automate the automation.2 -
Pressing that “deploy to production” button when it usually consists of multiple projects and databases updating at once.
Maybe I should look at separating them one year. -
In a marriage party.
Guy1: let's have the diner fast and run away. Have to deploy a very important update.
Guy2: brother, it's your marriage party. -
Allright, this one begs for a rant.
Me (Linux boi):
0 checkout code
1 update local config file
2 compile
3 deploy locally
4 run
5 use
Coleague (Windows boi):
0 checkout code
1 update local config file
2 compile
3 deploy locally
4 run
-1 "configuration xyz not found in config file"
→ goto #3
After 4 attempts:
ø windows.reboot()
3 deploy locally
4 run
-1 "configuration xyz not found in config file"
3 deploy locally
4 run
5 use
// out of curiosity...
3 deploy locally
4 run
-1 "configuration xyz not found in config file"
NO side actions taken (no configs updated, no code changes made, no nothing. Just simple double-clicking the redeploy script again and again)
Now... How do you objectively explain THAT?
http://weknowmemes.com/2013/01/... IRL :)8 -
Going live on Friday afternoon.
- no way, too many critical bugs! - I said
- we will - the Key account manager said.
Friday is here, still many critical bugs, I was right, it's impossible.
The Key account manager just dropped all functionalities with critical bugs and tricked the customer into thinking it's ok.
So we go live.
He was right, we can.
Oh yeah.6 -
Is it normal to deploy a 5.6MB main.css file?
Last week I had to change some shizzle on a website (externally developed).
Well, I was quite shocked...
We usually deploy a single stylesheet under 700 kB.
But also because we never use CSS "frameworks".30 -
When your week has been so busy and exhausting you remember at 1PM Friday you have a deadline for Monday morning and force yourself to do a weeks worth of work in 4 hours and deploy it on a Friday without QA testing!
To future me - I apologise for Monday’s headaches. -
it was 12am when we are ready to launch our new web design which requires a lot of hardwork and routing processes. my team lead was the one who pushes the button to production using "cap production deploy" command. everyone in the room (including PM) was like counting down like launching a rocket to space. the feeling is great knowing that everyone was sleepy at that time. im glad it went smooth and everyone congratulates each other.3
-
So ive been messing around with my Google Home.. because having a voice activated weather station is cool and all, but as a developer it needs to be useful no?... and Raspberry Pi, cause you know, we cool kids have those sitting around doing nothing useful.
But back on track, getting these two to actually work together, and that almighty moment you can say "Hey Google, Deploy Project -X- to the Pi" and the Rpi just kicks into gear and pulls down the latest master branch from Gitlab for the correct project is mind boggling.
No more ssh + sudo git pull !!!
Disclaimer: i didn't pay for that Google Home, but its in my house, listening to my TV, so i may as well use the damn thing.1 -
ENV: *runs flawlessly for months*
DEVS: *deploy a code change*
ENV: *crashes and bursts in tears*
DEVS: "PerfEng Team, your environment is broken! Please fix it ASAP" -
Deadline : Friday evening
Testing : There is only prod
Deploy : Friday evening
Why : Boss says customer wants it
Me : . . .11 -
!Rant
My boss just gave me a task "deploy this project today".
1. Made by a junior dev, and I have to take responsibility to upload it in this short time (no blame to jun dev, she's new and need to practice)
2. In a crm that I personally never used before, I need to study it and adapt at least the paths
3. Task was given at 13.48 during lunch pause.
But
But
The best is yet to come
Wait
.
.
.
.
.
.
.
.
.
.
Ready?
4. He doesn't know the server where to deploy it!
No one knows.
The IT doesn't answer, but still, I have to deploy a project TODAY (2h and 47 minutes left eob).3 -
My time in devRant is the time it takes for code to build and deploy. devRant is why I don't improve code performance 😎
-
You lousy fucking test class of an ass wipe,
TLDR; it fails and it passes all at the same time.
So during a deployment, one of the pre-deployment test classes fails, not something anyone has worked on so figured I run it manually to see what’s going on, but no the shit of a thing passed second time around.
Now because we can’t deploy without 100% of the test classes passing so I have to organise another deployment which it fails again. Fuck this,
Unprotects master
Git checkout master
Git merge dev
Git push master -f
Protects master
Skrew this!
Well would you look at that, it works now 😰 -
DBA bitches about one of our developers SQL... implement changes... deploy... now it takes 12 minutes... up from 40 seconds... good job!7
-
Quick reminder: don't deploy to production on you last working day before holidays :)
Wish you all happy new year)
GG!5 -
The intense moment when there are thousands of people eager to use a new website you developed and there are still bugs and rough edges but the launch time is in 2hrs.
Needless to say I'm pretty nervous. -
Last time I was here I was in college. 🤓
Hello world, again 🫂
I graduated and now I have a job as a developer for two years now.
So much ranting has been happening and I'm excited to tell you all about it.
PS: I already had my first canonical event (Prod deployment at 5 pm ... Was not fun ... Wasn't me if you're asking)1 -
Definitely Docker.
Do whatever you want, whenever you want.
The pinnacle of flexibility.
Try out everything, without installing anything.
Deploy with the same environment you're developing with on your local machine.
It's brilliant! -
Github is again down, I wonder if they triggered deploy from wrong branch.
Fuck this shit, moving to selfhosted solutions:
https://gitea.io/en-us/13 -
We were forced to do a Friday deploy of a new project. I, smartly, decided to bring my laptop with me on a "couples date". I spent the entire evening trying to fix a screwed up deploy from a restaurant.
Wife was NOT happy.2 -
My old boss used to deploy sometimes at the last second. I was about to walk out of the office (friday at around 5:30pm) when he said "Oh wait i wanted to deploy this website you've created" Before i could argue he deployed the website and ofcourse it broke in production..
This caused me to stay for another hour and a half in order to fix it...2 -
When you want to do a few test deploys (project going into alpha today) and your Internet is too slow to even login to the server 😭2
-
If you don't know, there are 2 types of bug fixes:
Hot Fix - Patch files directly on the production
Quick Fix - Deploy fix on production and then test it4 -
I'm preparing a major deployment & what do I see?
SOMEONE MANUALLY EDITED PROD AGAIN
IMO they deserve to be hit on their hands with a stick every time they even think of fucking with it.13 -
Promised to stay late to run a large deploy.
Now waiting for a large schema migration on a 7M row table.
4 -
So i just saw a post about not pushing to production on Friday's and that reminded me of something.
A team we are working with (we needed help on something so we got another company to send us a team and do it for us) recently push to production on a Friday at around 5pm.
We didn't know that they had done it until a shit ton of errors started happening and we had no idea why (it was working so far, none of us did anything, so what the fuck is going on).
To make things better, one of my colleagues tried calling them and they wouldn't answer the phone. They knew what they did, so they went home before we could notice it and we had to correct their mistake.
We had everyone calling us saying they had gotten an error, and they needed to get home but couldn't because of it (it messed up a process that only happens at the end of the day before people go home. I can explain more in the comments if anyone is confused, or just wants to know).
Eventually everything was solved, but that was a very stressful ending of the week.
So yeah, don't deploy on Friday's please and thank you7 -
So last week I really fucked up
I had this new implementation that was supposedly to be integrating smoothly into the rest of the service. It depended on a serialized model made by a data scientist. I test it in local, in QA environment: no problem.
So, Friday, 4pm, I decide to deploy to production. I check once from the app: the service throw an error. Panic attack, my chief is at my desk, we triy to understand what went wrong. I make calls with cUrls: no problem. Everything seems fine. I recheck from the app again: no problem.
We dedice to let it in prod, as the feature work. I go get some beers with the guys, to celebrate the deploy.
Fast-forward the next morning, 11am, my phone ring: it's a colleague of my chief. "Please check Slack, a client is trying to use the feature, it's broken"
FUUUUUUUUUUUUCK!!!
Panic attack again. I go to the computer, check the errors: two types of errors. One I can fix, the other from a missing package on the machine that the data guy used.
Needless to say, I had a fairly good weekend.
Lessons learned:
- make sure Dev, QA and Prod are exactly the same (use Ansible or Container)
- never deploy on a Friday afternoon if you don't have a quick way to revert1 -
Best: learnt how to deploy Wildfly application server from scratch on a live environment without messing up.
Worst: could not continue working because my internship was over. -
It's been a week since I last deployed the app and no bugs or errors reported by the client so far :)
What do you mean it doesn't count if the client isn't using the app? Ofc it does, fuck you >:(1 -
For the ultimate fuckit alias:
alias fuckit='git commit -am "$(curl -s whatthecommit.com/index.txt)"'
gulp && git add . && fuckit && git push && firebase deploy3 -
Kudos to Hetzner for approving my new account this morning, on christmas eve. Now I can finally deploy my new Minecraft server!3
-
myTechLead: We have to use Deno to this.
Dev: What about rails?
mTL: Deno, I said.
2 Weeks later: How can we deploy this stuff?4 -
I always hate that part of the project where you finish all the coding and start trying to deploy into production for the first time.6
-
When you do a deploy and none of the tests fail and you get more suspicious of the code than when a couple of them do fail.
-
Here: this is BDD, a Linter, and Git. CI your shit to staging before you CI to production. Never deploy on a Friday.
-
Two days ago I wrote the deployment instructions. 5 lines. I sent them to the devops four days before the release (two days before usual).
A colleague of mine leashed out and had me send another message to say to ignore my instructions because they "generated too much entropy" he is releasing too his application and we should create a single instruction file. Okay, I see no reason to do that nor how that helps the devops. A longer file is not easier to understand than a smaller one.
Today the devops deploy our application. They make a backup of the new files and promptly overwrite the original copies with the files from production.
I lost 3 hours today. My colleague is refusing to communicate the error properly to the devops and I have a meeting in 20 minutes. I love my job.3 -
*Finished the deploy*
*Dusts collar*
"Easy pesy"
Few hours later
*slack tone*
Production inaccessible! Blackbox crawler failed with message 5xx.
And that was the day little Charlie learnt dev-ops is not fun and thrilling. -
Hmm. This code needs refactoring.
*recodes on Local and uploads*
Works on my branch.
*git push origin master and merge*
Works on Dev.
*deploy to Test*
Works on Test.
*deploy to Live*
Doesn't work.
*compares Live to Test, Dev, and Local*
No f$@%^%%$# difference!?!!
*quits development and lives under a bridge*5 -
I am learning about CI/CD and DevOps, and i finally made my first build/deploy/unit test script.
I use arch btw6 -
Due to the surprising lack of rants, its either because people are just happy its the weekend... Or everyone had to deploy today against there will4
-
Took me an couple of days to reach this moment :')
Using MAAS to deploy to VM's, now time to get introduced to JuJu and see where it takes me :)
4 -
So we are preparing to deploy the changes onto production and some fucker decides to play with the fire alarm.
-
As the wise men once said:
You never truly know a framework before you can deploy without ripping your hair out. -
Midnight sever deploys and maintenance might kind of suck to do, but it is probably the closest we will get to going on a top secret mission!
-
They say "Don't deploy on friday".
That's why we, the part time student team, deploy on saturdays.1 -
I won't be surprised if MS adds a "one click deploy" button in GitHub projects to Azure cloud soon, which sounds pretty cool.1
-
How to manage updates on production as web agency
1: Update the GitHub private repo with your changes
2: Write an email to the customer sysadmin and ask to sync in staging and later production
3: Wait 2 weeks and do another ping about it
4: The sysadmin later will do that
5: In the meantime there is a security update of your CMS and a lot of plugins to update
6: Try to update from the CMS panel and there are no write permission
7: Cry a lot and write another email to go back to point 2 -
Thursday afternoon. Client gives us the go to deploy the latest release to production.
Friday late afternoon; my colleague - "wait, did we ever deploy"? Me - "uh, nope".
"Alright have a good weekend" -
I deployed to production in the middle of a zoom meeting with a client.
It was just a tiny change in the settings of a field that I 99% sure wouldn't produce any other major problem but we really wanted this client and we distracted them while the code was building.
Nerves racin all the way1 -
How to impress PM:
1. Prepare a critical bug, that makes the frontend crash
2. Prepare a hotfix, that fixes the bug
3. Deploy bug on Friday afternoon
4. Wait until PM starts panicking
5. Deploy hotfix after 5 min
6. Get praise from PM5 -
When you forgot to remove your debug description and add a real one before publishing your watchface :)
3 -
Why the fuck does android studio freeze on every 7th deploy. I just want a world where jetbrains can actually create useful IDEs please.4
-
I HATE that deploying every change takes like 5-10 minutes. I get so distracted and have such issues working efficiently. GAAH7
-
Finally found a way to deploy my Docker image to my VPS with nothing else than GitlabCI. My CI/CD system will soon be perfect.
[ Heavy breathing ]3 -
var rant: QuantumBool = PartlyTrue
So now I think I've got everything in my app right.... But I can't test it because ***** xcode doesn't create a **** certificate so I can deploy it to my phone (it uses motion sensors)
I deleted all the certificates of developer from the keychain because of a bug and now I **** can't deploy my apps for testing....
Please, does anyone know how to reset the icloud keychain to absolute nothing?7 -
Never! Deploy! To production! On Thursday! *banging my head against the wall*
Now I need to revert some things manually on production ON MY DAY OFF 🤦♂️🤦♂️8 -
Friday, forced deploy day for last & current months work. Been stockpiled due to holiday.
Yesterday boss demoed the product to clients so they expect to test today.
Early o'fuck this morning, a coworker managed to drop all secrets and env vars from CI pipelines and trigger a deploy leaving production broken...
It's gonna be a long and busy Friday... -
Fuck stupid VS, stupid M$, have to wait 20 min for Outlook to delete old emails in order to build - deploy solution
3 -
Monday: service deploy.
Friday evening: compilation and jar execution doesn't work anymore, on local machines or on server.
Nice.3 -
Heroku/Render
Deploy 2 apps
app #1 sends request to app #2 every minute
app #2 sends request to app #1 every minute
they never sleep
profit?5 -
Some things never change
> Have to deploy only one feature to production
> Create branch from latest tag, cherry pick the correct changes
> Mess up merge
> Almost deploy resulting broken code to production
> Realize at last moment
> Let out a loud sigh, start over
Every damn time.4 -
do you do any rituals to make it psychologically easier to deploy your code into production / replace an existing working system?10
-
F'ing bugs you find months after deploy that are so big it shouldn't have been missed, yet somehow dozens of eyes missed it.
Damn code gremlins -
Fifth server been created on amazon so i can finally deploy my laravel web app. Has been 3 days so far...
Fuck me5 -
This illustrates me perfectly, at that moment when i found that the project manager scrapped my updated lines in the deploy.
-
Favorite memories by far were the foosball, beer, ping pong, and subtitled foreign movies while we waited for code to deploy to test environments.
-
Deploy Updates in the production Server, when:
- it's Friday
- after lunch
- 2 hours before closing time
- the next 5 days are Holidays
-
Holy fucking shit.
Can people not break my shit mid deploy once, fucking once is all I am asking. 2 weeks of this shit. -
Attempting to deploy my web application using Heroku. It throws me error code H14 so I add scale web=1 to the web dyno per their documentation. I get this console log thrown at me after attempting to deploy.
I'm starting to get pissed. I may end up just dumping this and deploying my node.js/java application straight to my Linux server.
Edit: Or better yet start learning to use this Docker thing I keep hearing about.
5 -
Waiting for the day when i deploy my app to the production server and everything runs as expected.
1 -
I currently use Github as my git server and have worked a little bit with Travis. Sadly Travis can't deploy to local network targets and that's why I had the idea to create my own basic CI for the local network: It will be a simple nodejs-app and listens to pushes via Github Webhooks. Then it fetches the code from Github and runs a task runner like Gulp over it and tests it with any nodejs testing framework. Then it deploys the compiled, tested and linted app to the local network. What do you think of this idea?8
-
- Quit my job
- deploy my platform live!!
- make a dev tool
- move out
- get a cat
- start at least 1 successful business/application
Not in that order3 -
Okay, managed to negotiate with my manager to deploy our first Lambda + Golang service. Muehehe. Let's have some fun!!!5
-
I was planning a long rant about how AWS is so noob-unfriendly, but honestly I'm just tired after trying in vain to deploy a simple Django app on EBS with a simple RDS SQL db. Seven hours of not being able to deploy a simple Django app ffs 😭😭😭😭😭1
-
A developer couldn't get a application performance monitoring (APM) tool to trace his application. They claimed that their libraries and their configurations were alright and that the APM tool was non-performant.
The developer then argues with sysadmin that the APM tool can't trace the application and that there's nothing wrong with the application or the configurations. When sysadmin questions whether the developer got the tool to work anywhere, they say, "No" and head off to make it work at least in one place. They come back saying that it works on their development environment (which is their local machine). Sysadmin claims that the system configurations on the server instances cannot be matched by the development environment and there could be a lot more factors to be considered for the problem. The sysadmin asks to prove it on a server instance on one of the test environments and then they'd agree that it is a problem with the tool. They also argue that this is not the only application that uses the APM tool and the tool happily traces other applications with no issues.
The developer tries the same configuration on a staging instance and fails. In order to make it work, they silently uninstall the existing version of the APM tool and then compiles an unstable branch of the tool. It finally works with this version.
They go back to the sysadmin and show that it works on the staging environment, but does not on production. After banging their head on the wall for a while, the sysadmin figure that the tool had been swapped out for the unstable branch that was manually compiled. When questioned, the developer responds, "It works with this version on staging, so deploy the same version on production"
WTF? You don't deploy an unstable branch to production. Just because you can't make it work on the stable branch doesn't mean that it is the problem with the tool itself. There's a big difference between a stable branch and a non-stable branch. How would you feel if the sysadmin retorted by asking you to deploy the staging branch of your application to production? -
36 or sth..
Trying to fix production for xy client without them noticing someone fucked up everything with the previous deploy.. (wasn't me)..
Anyhow, managed to deploy my changes plus fix for the previous fuckup.. in the morning it all worked as it should.
Why it took me so long? Because why bother writing down what changeset was used for deploy.. It's much more fun to guess.. Multiple times.. Anyhow, I managed to figure approximate code for that deploy & merge my changes & fix everything.. + later found out looooads of uncommited changes on the guys computer.. :/ So yeah, never trust a bunneh!! -
Heroku. Deploy and forget. Good for beginners too. And the add-ons make it extra easy to find nice toys to add to your app2
-
There is a serious possibility that our team will need to deploy into prod on a Friday because of a regulatory deadline and 3rd parties not being ready.
God help us -
I have to deploy our software onto multiple raspberry pi so I started cloning an SD card with DD....devRant time I guess
-
Hmm. I've been wondering how I'll deploy an api based on a microservice style the smartest way... The general plan was to use salt to setup the base server and install dependencies and add the configuration.. Doing updates would be a git pull and pm2 restart api. I would love to know how you deploy your software ?1
-
Updating an aws lambda today, sls deploy, Error: that bucket already exists.
I know it does just use it! -
Deployed first time on Azure and it really hard to deploy lots of changes/setting need to done before publishing website.2
-
Hell will break loose even if you deploy your shit on monday morning and noone has anything else to do.
-
the moment when you've removed a progressbar in the layout but not reference in the code..
and android studio says "No chamges to deploy"
fml..3 -
so i was validating some user data using ajax in a facelets page.nothing was actually being validated when i deploy the application in tomcat..i thought it some sort of a bug on my code and after checking for the greater part of today i just couldnt find any bug.So i decided to deploy on GlassFish and it worked perfectly fine..fuck containers!!!1
-
Noob question
I’m trying to deploy my front end web app (my personal website) to GitHub pages.
In my app, I used react environment variables to store a api key I need in my app.
When I deploy my app with GitHub pages, will the app still be able to access the react env variables?
Let me know if that doesn’t make sense. Thanks!7 -
Just a quick question for ppl that deploy websites through FTP: how are y'all deploying your sites?
Which tools do you use?14 -
so i'm about to deploy admin application which doesn't have admins passwords hashed
after asking him, wtf dude?
he replied, no worries mate
fml5 -
deploying the apps in production...
Devs: i'm confident enough that i can do this. Docker? wtf, i know how to do it.
after successfully deploy in production, 30 minutes later...
Devs: Hey, team lead. I can't access the DB, why?
Team Lead: what? why? what did you do?
Devs: I just successfully deploy in production using the tutum interface deploy button.
Team Lead: Did you uncheck to deploy the DB again?
Devs: Thinking.... hmmmmm No?
Team Lead: Opppsss, that's good. We can't eat our lunch until we fix it. We need to deploy the db back-up again.
Devs: Did I delete the db?
Team Lead: No? probably not you? LOL's
Devs: But who?
Team Lead: It's tutum but it's your mistake to unchecked to redeploy the db before you deploy the apps :D
DevOps / Software Engineer => IT -
I'm setting up my Linux environment
This is what I'm thinking:
Dual boot: Arch(anarchy)/windows 10
Linux:
Xmonad ->
Parths terminal deploy ->
Vim ->
Snipmate,
NERDTree
Suggestions?4 -
Hugo framework:
1 hour to set it up
1 day to read the documentation
1 eternity to actually fucking deploy it5 -
Ops teams that are "assuring" stability of production by being the only ones who can click to deploy to Prod add no value.1
-
/* Don't forget to re-deploy application after every time daylight savings time change, before Monday at noon. */
-
When it's faster to just deploy the change to the test server than it is to test on the local test environment that never fucking works. #JustProgrammerThings
-
We have a full architecture deployed in a vm, and two teams works sharing it. All the apps were running as expected, the other team had demo and ask us not deploy anything in server....so we copy the war of our spring boot app to the server (23MB). Server collapse 10' before demo. We said that we weren't. I hate the other TL. I was happy.
-
Just wanted to say that netlify is so nice. Just 4 clicks and you continuously deploy your Frontend from a git repo. Even free for personal use 👌2
-
It's 05:30 and I'm about to leave for the office to do a deploy.
Morale is currently floating between "fuck off and die" and "confused Gandalf meme".2 -
WHY DOES EVERYTHING BREAK WHEN I WANT TO DEPLOY?
Finally fixed the last few bugs on my project and the thing is pretty much set to go. Then both the production and my local copy (identical in every way except for connecting to different MySQL servers) have the EXACT same query issues. The cursor fetch methods ALL get nothing EVEN WHEN I CAN SEE THE CURSOR HAS THE DATA I REQUESTED in the debugger.
I'm already in hot water for taking longer than expected with this project and this is going to push it back even further. -
Any ColdFusion devs in here? I've been plying with it for a while; Nice Java framework, quick to deploy. Feels like it could struggle under high request volumes though..?2
-
Runs automated deploy script on new laptop.
Forgot to install latest .NET.
And SQL Server.
And Node.
And… 🐢🐢🐢 -
Just found Deployd (a backend for applications). First framework whose marketing slogan I actually found to be true: 'deploy in minutes'.
-
Virus scan is crippling my computer, can't deploy till it's done! Might as well be using ticker tape to deploy these reports to the server.
-
As a front-end developer who has a firm grasp on web tooling, I still think the sheer amount of knowledge needed for dev-ops/deploy tools is staggering.
-
So it looks like pecl.php.net is down and I have about 6 hours left to deploy my new release... Any idea what to do? God I hate this job.4
-
Our Gitflow:
- kill bug
- pushes hotfix branch.
- deploy hotfix branch
- see if that solves the issue
- go back to the top if it doesn't
- merge hotfix into main and then deploy main -
Sometimes I deploy to production without actually testing the changes. At least I have my unit tests!
-
The best way to write secure and reliable applications? Write nothing; deploy nowhere.
https://github.com/kelseyhightower/... -
So of I want a devops bot for deploy it deploy himself or I need another bot to be a perfect DevOps??? Or Can I deploy it the old way?2
-
Every first of a month is our most intense day because we have the most data throughput then due to lazy people we get data from. And boy will it be even more intense when something broke because we were forced to deploy a new feature the day before...
-
Bribing sysadmin with an ice cold Coke hoping he will deploy my latest tag sort of in a hurry since I fudged up last one :/1
-
I must deploy a new solution today so my product owner came to ask if I finished and asked a new feature for today asap.
-
QA: Finds and reports Critical Bug
Dev: Hotfix 2 days before next scheduled deploy, NP!
After Scheduled Deploy...
QA: Critical Bug is back
Dev: Oops, overwrote hotfix during Scheduled Deploy -
Deploys to Production.
Runtime error.
Open Development server and run in Production setting.
Still runtime error.
Fixes Error.
Error fixed on development.
while (hoursWasted < 3) {
Deploy.
Not working on Prod.
Try other fix.
Still not working, but works perfectly in dev machine.
What the fuck
}
Rage
Go take a walk
Realized I might have deployed to the wrong server
Glanced at deployment path
Realized it's at the wrong server
Reconfigure and Deploy
It works.
Fuck.1 -
If you were to host a PHP website in a managed hosting, able to handle 200 concurrent users and upgrade to a better plan with no or small downtime if needed, which would be your choice?
The ability to integrate a CI/CD solution would be really helpful.
Context: We are dealing with a one-time campaign at the company and we don't plan to integrate this project into our architecture, so we looking for alternative solutions where to host it and deploy it to.5 -
Ok. If you had a blog made with next.js and mongodb, and you are too depressed and lazy to learn AWS lambda/serverless, where would you deploy?15
-
i want to deploy websockets on multiple servers with horizontal scaling. i don't know what to use. redis pub/sub? haproxy? i wanna know your opinions. ❤️6
-
Finally finished my 21h shift...Deploy on production is tomorrow...Back to the chair in a few hours.4
-
I just thought of an elegant solution to a problem in prod. Basically need to run 2 different versions of a app.
Just deploy it to uat and point it to prod db for the data.
I guess if we were following microservices architecture though we could deploy both versions to prod but we don't....3 -
DEBATE:
where do you deploy your web applications (node/rails/etc) on a linux server?
/srv -
/opt -
/var -
/usr/local -7 -
Watching CI builds run your tests and then deploy the passed version to thousands of users....oh, and the free hardware :)
-
Wanted to make an auto deploy script for nginx combined with git for websites i work on. Guess ill learn bash on the fly1
-
Does anyone use file comparison software (Ex. Beyond Compare) on production server to deploy code?7
-
MRW I deploy to production server and forget to add a server domain in "OAuth redirect domains" in Firebase.
Before that I was debugging for 6 hours without success.
1 -
I'm having colds since last night and a headache. But still need to deploy and check the ticket. Advanced Merry Christmas everyone. Please stay alive. We're not yet done.
Top Tags
Weekly Rant
View