Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Python

+ - Ask Slashdot: Taming a wild codebase: versioning and deployment suggestions

Submitted by tavi.g
tavi.g (816536) writes "Working for a ISP, along my main job (networking) I got to create some useful code (Bash and Python) that's running on various internal machines. Among them: glue scripts, Cisco interaction / automatization tools, backup tools, alerting tools, IP-to-Serial OOB stuff, even a couple of web applications (LAMPython and CherryPy). Code piled up — maybe over 20 000 lines, and I need a way to reliably work on it and deploy it. So far I used headers at the beginning of the scripts, but now I'm migrating the code over to Bazaar with TracBzr, because it seems best for my situation.

My question for the Slashdot community is: in the case of single developer for now, multiple machines, small-ish user base, what would be your suggestions for code versioning and deployment, considering that there are no real test environments and most code just goes into production ? This is relevant because lacking a test environment, I got used to immediate feedback from the scripts, since they were in production, and now a versioning system would mean going through proper deployment/rollback in order to get real feedback."
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Ask Slashdot: Taming a wild codebase: versioning and deployment suggestions

Comments Filter:

No problem is insoluble in all conceivable circumstances.

Working...