Le 30.05.2014 12:08, Chris Angelico a écrit :
On Fri, May 30, 2014 at 7:04 PM, <berenger.mo...@neutralite.org>
wrote:
What I basically want to do, and I do not understand how they ( my
programmer colleagues ) can happily live without that, is a server
for
source versionning, bug tracking, wikis, etc. This stuff does not
need any
virtual system or network, and is relatively easy to deploy.
Thanks to distributed version control systems (the current
generation,
with git and hg being the two most popular and full-featured), you
don't need a "source control server", so you can just start using git
on your own computer until someone else is convinced that it's
worthwhile.
That's what I did in my last job, and that's what I'm doing in this
one.
But... it is only efficient for the projects I have control on, not for
other ones...
And if you have a source repo, it's amazing how far you can get
without an explicit bug tracker - just keep a text file (or a
directoryful of text files, depending on how many bugs you're
responsible for) in your source tree. As you find and fix bugs,
you'll
change code and also update the BUGS file or directory, so it's
automatically linked.
Sure, but it won't avoid me to have to parse those f****** messy excel
files first. *This* is a real pain in my... heh... I feel quite lonely
sometimes: only real linux user, only guy using a really minimalistic
system, only tiling window manager user ( with the problems it pulls:
every one just do not mind using dirty tools. But I'm lucky --or
tinkerer-- enough to often be able to find better tools that works :p )
and only guy who knows about recent ways to manage source code.
All that thanks to free software world and my small contributions here
and there hehe.
Also, there's fossil if you are in that situation: it's
But I absolutely agree. Push for those kinds of features.
But, and it is why I need this virtual and iptables stuff, I would
like to
simulate the production environment of our main client. Would you
trust me
if I say that currently, testing ( beta ) and development ( alpha )
versions
of softwares are directly sent on production servers? It hurt me a
lot ( and
not only because it is bad and disgusting: it also makes everything
a lot
more complex ), so I want to have a replica of that network in our
own
network. 2 replicas, in fact, one for testing, and another for
programming,
so that automated tests ( which are currently lacking, too ) could
be made.
If you can't manage it with iptables, can you possibly do it with
virtualization? Build up an entire LAN on top of one computer - I'm
not sure about other systems, but recent versions of VirtualBox let
you easily connect multiple VMs together onto a virtual LAN, using
NAT
between that and the rest of the host computer.
The internal, virtual lan works perfectly: the virtual computers can
discuss together, it's damn easy to configure. Use a bridge network card
( or something like that in virtualbox ), configure some static
addresses without conflicts in their /etc/network/interfaces, and your
done. But they won't be able to access things outside their LAN ( for
this, you would need a router ).
Having the host communicating with them in that configuration is easy
too: just create a new entry in your /etc/network/interfaces using vlan,
give it a static address on the VLan which does not conflicts with
others, and it's ok, you can now use ssh, http, and whatever you
installed on your host from the guests, and vice versa. But VMs are
still not able to reach the real LAN, nor the real LAN to access the
VLAN, still need a router.
Since my host have a hardware ethernet card and a virtual one plugged
into the hardware one, I suppose that the way to allow the LAN to
communicate with the VLAN is to configure the host so that it will
become a router.
There are new replies in the thread that I did not had time to try, but
I have read them quickly, and I'm quite sure they'll push me on the good
road. I'll try to find the time when I'll have finished my more urgent
tasks (grumbl... urgent and boring tasks sigh).
It's not easy for a junior employee to make sweeping changes, even if
they are bringing the company in line with well-known best practices.
Yes, but I have some great advantages over most people:
_ I am really stubborn, and do not abandon my ideas without discussion
with real arguments. Political correctness is not a real argument for
me.
_ I like to say what I think the way I think it.
_ I have a small knowledge about how free softwares works, that kind of
projects where people are able to use one-shot contribution, from
distant guys they'll never meet. Unlike people who only know how to work
in the same open-space with phones ringing that often ( both have
advantages and problems, indeed, but only knowing one of them is quite
sad for someone which lives from dev ).
_ I'm lazy ( remember, I'm a dev :p )
_ I'm in a small enterprise, and my colleagues **seems** ( I don't
think they really are, they only claim to ) to be open to that kind of
things.
Some can obviously be problematic sometimes, but hey, my colleagues
deploy stuff by hand. When they do an error, they have to check by hand
and eye where the problem come from in their manipulations. I already
have seen them loosing more than one hour for that.
Me, on my side, I build a .deb, send it on distant computer through
scp, and dpkg it with ssh. Build a script with that, it is only 1
command, 20s. Configuration automatically updated. No problem due to
manual work.
That kind of facts enforce me in my positions, and anyway, I always
keep in mind a French adage: "We are always the asshole of someone." (
"On est toujours le con de quelqu'un." ).
If they do not want to follow my methods, well, ok, loose you time
guys, I won't.
Hoping to find something that you can do entirely under your own
control. :)
You mean, be your own boss? I already thought about doing something
like that, but having though about it shows me that I actually need some
more "real world" experience. Plus, being hidden being a job allows to
create your tools and hopefully future products on your own time while
being paid, so that when you can start the whole thing then you already
have everything in-place.
Finally, it's not that bad that this enterprise does have to tools, and
that I had the authorization to deploy some: it will allow myself to
play with redmine administrator's side, as well as to dig into the
various http servers, VLan problematics, etc, things that I could not
have made by myself otherwise.
Plus, I am really found of free software world, but I really have
doubts about any way to live from it when starting from nothing. If I
could earn enough time to find a way before starting, that would be
really nice, but it's another subject.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/28acbf24363f432510a2cab0ae0db...@neutralite.org
