Slashdot Mirror
Distributing In-House Engineering Code?
caswelmo asks: "My company has recently moved from Solaris workstations to Windows workstations (Ohhh, the humanity). As an engineering focused company, we use our computers to run many in-house (command line) codes to analyze and design our products. We currently use NAS storage to store everything and use batch files and init scripts to run the correct codes over the network. This makes sure everyone is running the latest version. This also stinks. I know this isn't an original problem, so what are some other solutions for rolling out lots of simple codes like this?"
I don't know what is worse - that you went to Windows, or you had no idea how the heck to go to windows.
I have mod points and I am not afraid to use them
I think that Windows ships with the QBasic scripting / operating system language.
/e command.com > com1"
From what I hear, it's quite capable for simple "shell scripting" style tasks in Windows like:
"command.com
and
"echo ^G"
Have fun!
Don't think that a small group of dedicated individuals can't change the world. It's the only thing that ever has.
step 1: move all that stuff into cvs / source control system of your choice.
step 2: install cygwin on all the machines (http://sources.redhat.com/)
alternately: use ms's unix system services (go digging on the m$ website) theoretically this will give you a "real unix" running inside windows.
at least this way you don't have to spend as much effort porting your old tools.
"My company has recently moved from Solaris workstations to Windows workstations..."
Didn't check it first to see if critical work could be done?
Okay, here's what you do:
1. Send the person who made this decision to Singapore to be caned;
2. Send his boss to Singapore to be caned and send the boss' dog for caning too as the dog may be the true decision-maker here;
3. Get yourselves someone who has more than a two digit I.Q. to be your boss;
4. Profit!
Ciao.
Everything in the Universe sucks: It's the law!
...anything about code:
...he/she refers to source code as "codes". At least that's what the rumors on the internets tell me!
As an engineering focused company, we use our computers to run many in-house (command line) codes to analyze and design our products. We currently use NAS storage to store everything and use batch files and init scripts to run the correct codes over the network. This makes sure everyone is running the latest version. This also stinks. I know this isn't an original problem, so what are some other solutions for rolling out lots of simple codes like this?"
OtakuBooty.com: Smart, funny, sexy nerds.
Make python executable (with py2exe) on shared drive, linked from win desktops as shortcut and launch on startup.
said script has dedicated local directory like: c:\ourscripts\
and synchs everything from the network at launch. Script remains running and checks via xml-rpc for updates and will throughout the day get updates to particular files. If you do the xml-rpc check every minute, you'll have near-realtime distribution of cli scripts to windows clients.
I am assuming you have less than 1k people to do that with in your org. One server could easily handle it.
by the way, redhat autoupdate uses xml-rpc.
This has the advantage not to need any local machine deployments of software packages.
Let me know privately if you need this sort of solution built. Or ask the python mailing list.
"Piter, too, is dead."
Actually, that indicates that it is really an engineering company. Among people whose first interest is science and programming is only a tool to solve scientific problems, it is common to refer to programs and libraries that solve specific problems as "codes". It is also a good bet that if it's called "a code", it's written in FORTRAN. And due to their science education, the authors were probably oblivious about principles of good software engineering.
That's all ok except for the CVS part. Use subversion and you will have it right.