|
|
| Line 1: |
Line 1: |
| − | This is the ProgClub [[news]] for the year 2012. Latest news goes on top.
| + | Building a Rat Rod - The Easy Way |
| − | | + | |
| − | = 2012-04-19 =
| + | So your a beginner at this kind of car building thing and the first car you choose to construct is truly a Rat Rod. That is a good choice as you can "cheat" somewhat a lot more than doing a 100% restoration. Here's a couple ideas to help you get started. |
| − | | + | |
| − | == New member ==
| + | Depending on exactly how much your really understand about cars or Rat Rods, since a beginner you may choose to come across a good "roller." A roller will be a complete body that offers suspension, but doesn'testosterone have to have the engine or trans. If you feel somewhat far more advanced, than you can begin building your car from a frame upwards. Mixing and matching parts through different models and producers will be the Rat Rod way. |
| − | | + | |
| − | ProgClub welcomes [[User:Lulu|Lulu]].
| + | Great is the way to go. Rat Rod designs are very simplistic, but how to make it awesome is by combining the right amount of parts with the right car. Installing a fuel injected engine through your Toyota Camry is actually not the way to develop a Rat Rod. Installing a contemporary Corvette rear suspension is additionally not just how to go. What we should are trying to express below is carry on it former and simple. |
| − | | + | |
| − | = 2012-04-11 =
| + | Most rodders that had been doing it for decades realize what parts consult with each other. In case you are starting out, use parts within a 15 year span. Maintain a 30'utes vehicle using 30'utes or even some 40's parts, 40'utes with 50'ersus and so on. |
| − | | + | |
| − | == jsphp.co developments ==
| + | Front Finish: Keep your grille shells but lose the front fenders and hood on your Rat Rod. Your want to find out your engine when it'ersus the heart of your respective Rat Rod. It'utes appealing to determine a Flathead Ford or a Buick Nailhead motor dressed way up with three carbs or elderly funky designed ingestion manifolds. There is nothing wrong with a good outdated Chevy or ford modest block. You can dress way up a 350 Chevy coming from the 90's to take a look because if its own through the 40's. Many parts are available, and at very reasonable prices. Many 70'utes through 90's car have them and they usually are a dime a dozen. Easy motor/trans swaps, and many people sell mounts and mount kits for them. |
| − | | + | |
| − | There is now a [http://jsphp.co/javascript/php/page/demo demo] and a [http://jsphp.co/javascript/php/page/faq FAQ] at [http://jsphp.co/ jsphp.co]. Also a Wikipedia article on the [http://en.wikipedia.org/wiki/jsPHP jsPHP] library.
| + | So what exactly you need to do today to get your Rat Rod Project started will be come across yourself the car of one's ambitions. Don'n run into it while if you appear hard enough, you will locate a deal. A negative economic system means a good price for your fresh Rat Rod Project. |
| − | | + | |
| − | = 2012-03-20 =
| + | http://www.arossisalon.com/index.php/member/5566/ |
| − | | |
| − | == New member ==
| |
| − | | |
| − | ProgClub welcomes [[User:Dachoi|Dachoi]].
| |
| − | | |
| − | == SanguineV working on [[pcad]] ==
| |
| − | | |
| − | Thomas has made [https://www.progclub.org/pcrepo?view=rev&revision=1294 another check-in] for the [[pcad]] software. According to his commit message: Server is now multi-threaded/forking. Should handle load a lot better and tidy up properly.
| |
| − | | |
| − | Thanks Thomas, very cool!
| |
| − | | |
| − | = 2012-03-02 =
| |
| − | | |
| − | == Adriano working on pcphpjs ==
| |
| − | | |
| − | [[User:Adriano|Adriano]] has been working on [[pcphpjs]] and disabled anonymous comments in addition to clearing out the recent spam on the [http://jsphp.co/ jsphp.co] website. Thanks Adriano!
| |
| − | | |
| − | == Updated navigation menus ==
| |
| − | | |
| − | The main navigation on the ProgClub wiki and blog has been given a minor overhaul and now it should be a little more useful and intuitive than it used to be.
| |
| − | | |
| − | = 2012-02-28 =
| |
| − | | |
| − | == Announcing the ProgClub Comms Bonus scheme and last year's winners ==
| |
| − | | |
| − | The [[Comms Bonus|ProgClub Comms Bonus]] scheme has been instituted wherein biannually selected members are awarded at least AU$200 off their communications bills.
| |
| − | | |
| − | The ProgClub Comms Bonus recipients for the period July to December 2011 are:
| |
| − | | |
| − | * [[User:Tasaio|Tasaio]], for: contributing to the mailing lists and helping with system administration.
| |
| − | * [[User:Key|Key]], for: contributing to the mailing lists, [[Mail_filters|contributing]] to the wiki, contributing to her [https://www.progclub.net/~key720/ MemberNet] and [https://progclub.mobi/~key720/ MobileNet] sites and hacking on the [[pcmnet]] project (including [https://www.progclub.org/pcrepo/pcmnet/trunk/ code] and [[pcmnet|documentation]]).
| |
| − | | |
| − | Congratulations Tasaio and Key!
| |
| − | | |
| − | = 2012-02-19 =
| |
| − | | |
| − | == jj5-bin added as standard to all user accounts ==
| |
| − | | |
| − | I have a project, jj5-bin, to create a whole heap of standard utility scripts to do bits and pieces. The scripts live in /home/jj5/bin. Until recently this was a ProgClub project, but for security reasons, given that this software is now automatically updated on my jj5.net and Blackbrick servers in addition to the ProgClub servers, I have moved the project into my private repository (it still has public read access) at:
| |
| − | | |
| − | * https://svn.jj5.net/svn/public/jjrepo/jj5-bin/trunk
| |
| − | | |
| − | So now there's a process for managing the contents of my /home/jj5/bin directory on all of the jj5.net/Blackbrick/ProgClub (and potentially other) servers that I use.
| |
| − | | |
| − | Particularly, as part of the jj5-bin project, there are .profile and .bashrc extensions for making aliases and functions available in a typical login environment, and also to script all sessions by default.
| |
| − | | |
| − | Session scripting means that all input and output to your login session (except passwords and other secrets) is automatically logged to a file for each login session. I find this really handy for: a) remembering what I did, and, b) referencing for documentation purposes. There are a few standard utilities that I've included for session management, and these are:
| |
| − | | |
| − | * note: type 'note' followed by a note for your session that you might like to be able to search for in the future. For example, if you're configuring your server with subversion, then maybe type a note like 'note installing subversion' so that later you can search for sessions where you installed subversion.
| |
| − | * session-search: you can search your session notes using session-search. For example, to search for your subversion installation session: 'session-search subversion'.
| |
| − | | |
| − | There are a few other session management facilities, but they're not all complete yet, so I'll document them later. Basically the documentation for jj5-bin hasn't been done yet, I'm still working on all that.
| |
| − | | |
| − | Anyway, I thought it was important for everyone to hear about this new project, because it has been configured as standard for everyone's account. That means that your ProgClub logins (and Blackbrick logins if you have them) now have the jj5-bin features, including the session logging.
| |
| − | | |
| − | If you're a ProgClub administrator the policy is that you have to run with session logging whenever you're administering ProgClub systems. Other users don't have to run with session logging if they don't want it, and the easiest way to disable session logging for your current session (and any other sessions where you're logged in on the same box) is to type:
| |
| − | | |
| − | pkill script | |
| − | | |
| − | If you do that session logging will be disabled for the rest of your login session, for all current login sessions.
| |
| − | | |
| − | If you're a ProgClub administrator: you can use pkill script in your own session if you don't want to leave a record of what you're doing, but never run pkill script as root, and if you're logged in as root or using sudo commands then you should leave session logging enabled. Also, if you're doing sysadmin on ProgClub boxes, then you should use the 'note' facility to make notes about what you are/were working on.
| |
| − | | |
| − | By default session logs are private for each user, so the only people who can access your session logs are yourself and ProgClub administrators. You can get a list of the current ProgClub administrators on the Members page of the ProgClub wiki. As a general rule it is OK for ProgClub administrators to snoop around in session logs to see what's been going on (especially in other ProgClub administrator's session logs), but it's still not OK for ProgClub administrators to read users' email or private MySQL databases.
| |
| − | | |
| − | Since all Blackbrick staff also happen to be on this list too, I'll just mention briefly that I'm in the process of applying the same standard as above to all Blackbrick servers, and for Blackbrick servers (which are for work, not for play) all users are required to use the session logging facility. This is not technically enforced at the moment (though in the future it may be), but the policy says to leave session logging enabled, so you should. If you have something to do that you need or want privacy for then use a ProgClub server and cancel session logging with pkill script.
| |
| − | | |
| − | If you don't like the sound of any of this (i.e. having jj5-bin utilities automatically added to your environment and logging your session activity) then you can edit your .bashrc and .profile and remove the last line of each, but if you're a ProgClub administrator don't do this, ProgClub administrators will have to stick to pkill script for the time being if they want privacy (and they shouldn't claim privacy while doing sysadmin work for ProgClub).
| |
| − | | |
| − | So, that's about that.
| |
| − | | |
| − | Your session logs are kept in your home directory in the .session directory. You can chmod 755 your .session directory if you'd like to share your session logs with other (non-administrator) users. ProgClub administrators shouldn't share their session logs with non-administrator users, because the content of their session may include personal data about members or things that should otherwise generally not be disclosed (e.g. you do something silly like cat or hex dump a .rnd or private key file and reports its contents in your session). | |
| − | | |
| − | The jj5-bin config, scripts and binaries are all kept in /home/jj5/bin and you'll find all sorts of stuff in there if you go looking, so do feel free to have a poke around. A lot of the jj5-bin stuff is for jj5.net and Blackbrick environments, so not useful to ProgClubians (except if you're looking at how to do something particular which you might find an example of), but as time goes by there will be more and more facilities in there, and hopefully a few of them will be useful for everyone.
| |
| − | | |
| − | I guess the last thing I will mention is that as a bonus the jj5-bin session login facility prints out some useful information at the start of every session, including when members were last seen logged into that box and who is currently logged in. If you have any suggestions for other useful stuff that could be included just let me know.
| |
| − | | |
| − | Oh, and on that last point, if there's something about this standard environment that bothers you, or that you think should be changed or is missing, then let me know and I'll look into fixing things up for you. Either by re-writing the functionality for everyone, or by special-casing considerations for your user/machine context, as may be appropriate.
| |
| − | | |
| − | = 2012-01-30 =
| |
| − | | |
| − | == New member ==
| |
| − | | |
| − | ProgClub welcomes [[User:GlennWilliamson|GlennWilliamson]].
| |
| − | | |
| − | = 2012-01-29 =
| |
| − | | |
| − | == New members ==
| |
| − | | |
| − | ProgClub welcomes [[User:Bri|Bri]] and [[User:Adriano|Adriano]].
| |
| − | | |
| − | = 2012-01-27 =
| |
| − | | |
| − | == Policy updates ==
| |
| − | | |
| − | The [[constitution]] has been renamed as the club's [[charter]] to avoid potential confusion given that our new company ProgClub Pty Ltd also has a constitution. Also John has nominated a successor for the position of [[Benevolent Dictator]] being [[User:SanguineV|SanguineV]].
| |
| − | | |
| − | = 2012-01-25 =
| |
| − | | |
| − | == Happy 6 months! ==
| |
| − | | |
| − | Today ProgClub is 6 months old. Happy birthday ProgClub! Over the past 6 months ProgClub has completely established its online services, made three computer systems available for members' use and had 19 members join. We've had a Christmas party, 197 blog articles, 436 mailing list posts to our primary email list, 111 pages on the wiki, four people with MemberNet pages, a number of members getting involved in club programming activities such as [[pcmnet]] and [[pcad]] and we've formalised our club under the governance of a company: ProgClub Pty Ltd. The progclub.org web-site has seen 4,978 unique visitors, 11,318 visits, 124,052 page impressions and 174,807 hits. It's been a productive 6 months!
| |
| − | | |
| − | To recap, that's:
| |
| − | | |
| − | * 174,807 hits
| |
| − | * 124,052 page impressions
| |
| − | * 11,318 visits
| |
| − | * 4,978 unique visitors
| |
| − | * 1,234 commits
| |
| − | * 436 mailing list posts
| |
| − | * 197 blog articles
| |
| − | * 111 wiki articles
| |
| − | * 28 projects
| |
| − | * 19 members
| |
| − | * 6 months
| |
| − | * 4 MemberNet pages
| |
| − | * 4 sys admins
| |
| − | * 3 programmers
| |
| − | * 3 servers
| |
| − | * 2 MobileNet pages
| |
| − | * 1 Christmas party
| |
| − | * 1 company
| |
| − | * 1 sponsor
| |
| − | * 1 club. The club. ProgClub.
| |
| − | | |
| − | = 2012-01-19 =
| |
| − | | |
| − | == Announcing ProgClub Pty Ltd ==
| |
| − | | |
| − | Rather than being a wishy-washy club with no clear legal entity or owner ProgClub is now operated by ProgClub Pty Ltd. ProgClub Pty Ltd is an Australian company that receives sponsorship money from Blackbrick (and in the future potentially other sponsors) for the purposes of operating the club. Blackbrick and ProgClub Pty Ltd are in the process of negotiating the sponsorship terms and this will entail formal transfer of ProgClub assets to ProgClub Pty Ltd who will own them and operate them for the benefit of the club. The details of this formalisation will be made available when the sponsorship agreement is finalised. ProgClub Pty Ltd is owned by [[User:John|John Elliot]] and John Elliot is the sole Director, Secretary and Public Officer of ProgClub Pty Ltd. Basically John's new company has been set up to operate ProgClub. The company was registered with ASIC on the 19th January 2012.
| |
| − | | |
| − | = 2012-01-12 =
| |
| − | | |
| − | == Server upgrades ==
| |
| − | | |
| − | Both of the user machines [[hope]] and [[charity]] have been upgraded from 256MB slices to 1024MB slices. MemberNet should be a little snappier now.
| |
| − | | |
| − | = 2012-01-07 =
| |
| − | | |
| − | == Pcad progress ==
| |
| − | | |
| − | [[User:SanguineV|Thomas]] has contributed a first cut OCaml version of the [[pcad]] system. Check out [https://www.progclub.org/pcrepo/pcad/trunk/src/ml/ the code].
| |
| − | | |
| − | = 2012-01-01 =
| |
| − | | |
| − | == Happy New Year! ==
| |
| − | | |
| − | Happy New Year everyone! Hope you all had a great holiday, and here's to an awesome and prosperous 2012!
| |
Building a Rat Rod - The Easy Way
So your a beginner at this kind of car building thing and the first car you choose to construct is truly a Rat Rod. That is a good choice as you can "cheat" somewhat a lot more than doing a 100% restoration. Here's a couple ideas to help you get started.
Depending on exactly how much your really understand about cars or Rat Rods, since a beginner you may choose to come across a good "roller." A roller will be a complete body that offers suspension, but doesn'testosterone have to have the engine or trans. If you feel somewhat far more advanced, than you can begin building your car from a frame upwards. Mixing and matching parts through different models and producers will be the Rat Rod way.
Great is the way to go. Rat Rod designs are very simplistic, but how to make it awesome is by combining the right amount of parts with the right car. Installing a fuel injected engine through your Toyota Camry is actually not the way to develop a Rat Rod. Installing a contemporary Corvette rear suspension is additionally not just how to go. What we should are trying to express below is carry on it former and simple.
Most rodders that had been doing it for decades realize what parts consult with each other. In case you are starting out, use parts within a 15 year span. Maintain a 30'utes vehicle using 30'utes or even some 40's parts, 40'utes with 50'ersus and so on.
Front Finish: Keep your grille shells but lose the front fenders and hood on your Rat Rod. Your want to find out your engine when it'ersus the heart of your respective Rat Rod. It'utes appealing to determine a Flathead Ford or a Buick Nailhead motor dressed way up with three carbs or elderly funky designed ingestion manifolds. There is nothing wrong with a good outdated Chevy or ford modest block. You can dress way up a 350 Chevy coming from the 90's to take a look because if its own through the 40's. Many parts are available, and at very reasonable prices. Many 70'utes through 90's car have them and they usually are a dime a dozen. Easy motor/trans swaps, and many people sell mounts and mount kits for them.
So what exactly you need to do today to get your Rat Rod Project started will be come across yourself the car of one's ambitions. Don'n run into it while if you appear hard enough, you will locate a deal. A negative economic system means a good price for your fresh Rat Rod Project.
http://www.arossisalon.com/index.php/member/5566/
