Basically, yes. You can configure most cron programs to mail task output to you (it’s usually done by setting the MAILTO variable in the crontab, provided sendmail is available on your system).
I use that to do things like:
0 9 11 10 * echo 'lunch with John Doe at 12:20'
It sends me a mail, and I can see the upcoming events with crontab -l. If it’s not a recurring event, I then delete the rule.
My favorite cost cutting tip is to avoid big webapps running on docker, and instead do with small UNIX utilities (cron instead of a calendar, text files instead of note taking app, rsync instead of a filehosting dropbox-like app, simple static webserver for file sharing, etc). This allows me to run my server on a simple Raspberry Pi, with less than 500mb of used RAM in average, and mininal energy consumption. So, total cost of the setup:
With that, I run all services I need on a single machine, and I have a backup plan for recovery of both hardware and software.
Getting used to a UNIX shell and to UNIX philosophy can take some time, but it’s very rewarding in making everything more simple (thus more efficient).
I have both a resin printer and a FDM printer, I can confirm the price difference exists, but is not prohibitive (resin is about 2x PLA). The difference of quality is mind blowing, though (in favor of resin printer). If you’re building an army, I assume you will have many pieces? If so, the difference of printing time is also mind blowing in favor of resin printer. The reason for that being that if you print 10x the same mini on your build surface, with FDM it will take 10x the same time as a single mini (the printing head must move to cover each point) while with the MSLA (resin printer), it will take… 1x the same time. That’s because each layer is flashed from a PNG image, so all points of a layer are created at the same time. On top of that, there are things you can do with resin that you just can’t with FDM, especially because of supports needed for hanging parts : if your character has arms, chances are the hand will be lower than the shoulder, which means than when printing from bottom to top, the hand won’t be connected to the body until printing reaches the shoulder, so you need something to support it (a “tower” under the hand, that you will cut off). It’s easy to do with resin, because in a bath of dense liquid, Archimedes is your friend and you can build the support in wild angles, but it’s way more difficult in thin air (with a FDM).
An other thing to know, though, is that resin printing is way more messy. You will manipulate toxic products, that you can’t throw in the sink, you need gear to cover your hands and face, and resin ends up everywhere and is near impossible to clean. But it’s worth it, especially if you’re into minis. :) FDM, on the other hand, is unbeatable for functional prints (because those resin prints are damn fragile, and tend to not be perfectly at the scale you designed).
Oh, I see. Yes, that may very well be a matter of point of view. For me, modding the printer is part of the fun, not something I do to try desperately to stay on the cutting edge. :) The RepRap dream of “printers that can reproduce themselves” never fully materialized, but modding is the next best thing.
Are they still sold, anyway? I mean, sure, someone who has no printer should buy a more recent one. But that was not the subject, here : the question was if it was needed to replace an Ender 3. I certainly would not, personally, it would be throwing out a perfectly good printer for incremental upgrades. Of course, it depends on the usage. For someone who uses their printer professionally to serially print all day, sure, it’s probably worth it upgrading. Me? I really don’t care if my prints are slower. I really don’t find the Ender 3 hard to get a print right either. But I’ve been printing since the wooden Printrbot Simple about a decade ago, maybe I’m just used to it.
I’m using a pi4 8gb as my server, with a pi4 2gb as backup in case the first one dies. It’s a very classic server, running postfix/courier-imap for mails, lighttpd for web, bind9 for dns, ergo for irc, sqlite3 for databases. I also use fail2ban for IDS and cron to run tons of various task. All of that is hosted on a Gentoo linux OS.
The one thing I don’t want to use is docker. I love docker for development or for deploying the main app at work, but it makes managing updates a nightmare for handling multiple services on my server (most your containers probably contain vulnerable software due to lack of system updates), and it eats resources needlessly. Then again, it’s made possible because I avoid the big webapps that usually need it.
At the very least, it means the CEO doesn’t understand the domain. It may be because he sees this part of the business as secondary and less important, or because it was developed so fast he didn’t have time to grasp the concepts, probably he was not a driving force in that effort. I certainly hope the tech side is more aware. Without more proof of CEO implication, I certainly would not bet on that horse to survive in the distant future, though.
“Git hosting” would be more appropriate. Unless that by frontend, you mean specifically web frontend, but that would be weird, because forges also provide the web backend part.
Sourceforge was the biggest FOSS host in the 2000s, before GitHub (mainly because there was not much centralization to begin with). That train is long gone. :) Sure, the name and website Sourceforge still exist. Myspace, Digg and Yahoo do too. They are basically web ghosts, only an echo of what they once were.
Actually, I do use git bare repos for CD too. :) The ROOT/hooks/post-update executable can be anything, which allows to go wild : on my laptop, a push to a bare repos triggers deploy to all the machines needing it (on local or remote networks), by pushing through ssh to other bare repos hosted there, which builds and installs locally, given they all have their own post-update scripts ; all of that thanks to a git push and scripts at the proper paths. I don’t think any forge could do it more conveniently.
For me the main interest of forges is to publish my code and get it discovered (before GitHub, getting people to find your repos hosted on your blog’s server was a nightmare). Even for the collaboration, I could do with emails. That being said, most people aren’t on top of their inbox, in which mails from family are mixed with work mails and commercial spam in one giant pile of unread items, so it’s a good thing for them we have those issue trackers.
^^
Oh, my apologies, Sourceforge! Say hi to Myspace for me!
That’s the name we use to designate software like GitHub, GitLab and similar, which provide repositories hosting and tooling like issue trackers. It’s supposed to be named like that because of SourceForge, the oldest of such tools, although I didn’t hear the term “forge” before the last 5 years or so, long after SourceForge demise, so I imagine there is a bit of nostalgia in this name (not sure who is nostalgic of SourceForge, though 😂). The wikipedia page : https://en.wikipedia.org/wiki/Forge_(software)
The worst part is that this is a direct quote from Harness’ CEO, not from TechCrunch author. :) Maybe they have a great product, I don’t know, but it certainly feels like an amateurish launch. :D
There hasn’t been a new Git repo launch in almost a decade
Am I the only person annoyed they seem to mistake repositories for forges? It’s already annoying when casual users say “git” for “GitHub”, but those guys actually want to build a forge, explaining they’re going to do better than anyone else. Maybe start by properly using the terms?
Has there been so much going on in the market? I’m still using my Ender 3 and I’m not sure what I would add to it, it serves me well (I already added a BL Touch, in the early days I got it, and a glass bed, although I don’t see much benefit from that last part). It’s just doing the job perfectly. 🤷 That being said, I only use it for functional printing. I way more often use my Elegoo Saturn (a resin printer), as I use it to print my tabletop minis.
Yep, as often, the extension of the standard comes from non standard features developed here are there (as you can see in the participating organizations block, most of the big names are working on this). The difference in ircv3 is that you can expect to see all those features everywhere, instead of having this software implementing this feature, that other one having that other feature, and you have to choose which one is the most important for you. Basically, it’s a rebase of the standard. :)
They do maintain the simplicity of the line oriented protocol, so I’m fine with that. :)
That’s the strongest point of IRC, IMO, and why it’s kept so simple : every instruction is a plain text line, period. It makes it incredibly simple to build on top of it. You don’t need to introduce a dependency to a project that probably will be abandonned in a few years, at which point you’ll have to rewrite your codebase to use an other dependency, for a few years. You just open a TCP connection, you read lines from the socket and write lines to it, each line is its own instruction structured in well known fields, and that’s it. It’s so simple!
As long as IRCv3 sticks to that, they have my blessing. :)
The good news is that with ircv3 being worked on, it may soon(ish) be quite dusted. :) It adds features like reply threads, history from when you weren’t connected, message editing and deletion, and more!
Take back the control on your data, that’s the whole point… :) Where are you regularly saving data? Those are the prime candidates. Look at self-hosted alternatives for those services. I know big webapps hosted in docker containers managed by kubernetes is all the rage around here, but you can often find Unix style equivalent for such services, the main advantage of putting it on a server being to be able to access it from multiple devices. But you do you, if you prefer hosting big webapps, that’s fine too. :)
I organize my crontab by having group of tasks (the programs, the holidays, the housecleaning, etc). And of those groups, the events (the non recurring tasks) come last. So I just list the crontab (crontab -l) and the list of things to come print to the screen, that block being at the end of the file. It’s hard to do better than a text file to list things. :)
I don’t know if there is a program that lists like “what is coming this month” if you really want to filter out the rest, but it should be easy enough to write, given the format of cron rules:
crontab -l | grep '*' | awk '{print $4 "," $3 "," $2 "," $1 " " $0 }' | sort -n | grep -E "^$(date '+%-m')"
crontab -l : list the crontabgrep '*' : keeps only rules (removing blank lines and comments)awk […] : print the whole line ($0), prepend by the 4th field (the month), the 3rd (the day), the 2nd (the hour) and the 1st (the minutes)sort -n : sort everything numerically, so that all tasks are now in their execution date order (I made awk seperate the fields with a , character so it keeps sorting numerically past the first number)date '+%-m : prints the current month, not zero padded (thanks to the ‘-’)grep -E '^date' : keep only lines which starts with the current month numberYou put that in a script (like ~/bin/upcoming_events) and you’re done. And then, you can call it from cron every monday get what’s coming next mailed to you. :)
This could but refined further to display dates in a more friendly format. But as usual, Unix is your friend. :)
That’s the same thing. :) If you reduce computing load, you reduce the need for costly hardware and you reduce the need for energy, thus you reduce the amount of money needed to build and run your setup. There’s a saying in (software) engineering : “reducing energy consumption and increasing performances requires the same optimizations”. Make your code faster (by itself, not by buffing up hardware) and it consumes less energy. Make your application simpler, and it will run faster, and it will consume less energy. It’s not an absolute truth (it sometimes happen that you make your code faster and it consumes more energy), but it’s true most of the time.