Use Arduino inputs to control LEDs in a non-trivial way.
– Project instructions
About a week ago I had the opportunity to attend BrickHack, one of the Major League Hacking hackathons. Ironically, I was attending this representing [email protected] as a sponsor despite this being my first hackathon. Meeting new people is always fun, and also I got to meet people I’ve seen around campus a lot but never interacted with. Explaining [email protected] can occasionally be a little awkward since we don’t have any particular big group projects, but are rather a community of people working on different things (and despite members having good projects (some of which they could get involved in), hearing that the group as a whole doesn’t work on any projects turns away some people – you can literally see them lose interest when they hear that). You also get those cringe-worthy moments when someone mistakes your group’s work, such as LibreCorps, an initiative which works with organizations like UNICEF, with LibreOffice, a piece of software (which is FOSS, but unrelated to the initiative). However, we were able to explain FOSS to a good number of people, mentioning how much of the software they use is FOSS, and how “free as in cost” is not the same as “free as in freedom.” We also were able to hand out most of the stickers that had been accumulated over time, which I know will make at least one person very happy.
The only regret I have is that we had a shift we were there for, and I would have liked to spend more time there. We didn’t know at the time, but when we were talking to one of the organizers after we found out that we could have. Next year I’m planning to attend again, but this time have it arranged for the [email protected] table to be a place for us to hack at just like the other ones, and also get some time to chat with the other sponsors and participants. Despite that, this was a good experience for me to learn about promoting a group’s work and running an event from this angle, which doesn’t participate in nor run the “main event,” but is still there actively interacting.
A DMZ (“Demilitarized Zone”) is an isolated network segment, usually used for public-facing servers to keep anything that may go awry on them from being able to damage the rest of the network.
The rest of part 4 is coming, but 4-2 and this were moved forward due to complications and over-scoping.
In addition to being a guide on running Collabora Office/Online as a package instead of a Docker image, this is the first blog version of my late night rants in the #rit-foss Freenode channel.
Having someone to introduce you to something always makes life easier. Whether it’s a tutorial on a piece of software, introduction to a group, or something more exotic, being introduced by a person allows for the comfort of someone who knows how to navigate the waters already and help correct anything that might go awry on the fly.
Just having a router is a rather boring use for a home lab server. Time to add a NAS, Docker, and a LAMP setup.
It’s time to install everything and do some tweaks to make life nicer. Also, a list of issues I encountered and how to go about resolving them. I’m going to use a lot of links to skip over most of the installation process, it’s fairly well documented (and the configuration is the more interesting part).
This is the start of the documentation for servers. As such, I figured it’d be best to give the background info for what I’m working with.