Lullabot

Apparently the one downside of Borg is that it has to walk the whole filesystem for backups, rather than picking up changes: https://github.com/borgbackup/borg/issues/325 According to a more up to date comparison[1] (recommends Arq), Borg is also slow because it processes sequentially. [1]: https://www.lullabot.com/articles/backup-strategies-for-2018

For what it's worth, Drupal is only more vulnerable if you install third-party modules that are vulnerable and don't update those, as well. If you happen to be interested (which I hope you are, since you brought up the subject of Drupal security), see http://www.lullabot.com/node/383 for a thoughtful take on the open security model.

Definitely start with MAMP, in my opinion. As it doesn't build/install anything itself, it keeps your system ultra clean. If you need to move beyond it, just drop it in the trash and you're done. A few hints: - By default, the apache doc directory is mapped to an os directory inside of the MAMP folder. Change this to something in your ~ directory right away so that if you upgrade MAMP, you won't accidentally write over your work. - Make sure MAMP dirs are at the beginning of your shell path because there are conflicting binaries pre-installed in OS X (basic, I know). - In my opinion, the MAMP PRO upgrade is worth it. It gives you much finer control over many things. - I've only compiled and installed the memcache pecl extension and I did that through the standard make/install process and it worked fine. I just had to drop the memcache.so file into the proper directory and find the right php.ini file to edit to enable it. See this post (and my comment -- 2nd from the end -- to see how to configure MAMP PRO): http://www.lullabot.com/articles/setup-memcached-mamp-sandbox-environm… Note: I did not use their process to build the extension, I used this: http://www.ibm.com/developerworks/opensource/library/os-php-fastapps3/… . - I don't think there is strong support for php pecl extensions in MacPorts, but MacPorts is great for a great many things. For example, I used it to install the memcache daemon. I hope that helps.

Drupal works very well as a headless CMS now https://www.drupal.org/docs/develop/decoupled-drupal https://www.lullabot.com/resource/decoupled-drupal Drupal has a really strong community behind it, and was completely rebuilt a number of years ago with modern PHP. It uses Symfony, composer, etc.

it's a valid question. In the JavaScript / TypeScript community, we usually understand "fullstack" as "isomorphic": https://www.lullabot.com/articles/what-is-an-isomorphic-application Laravel and RoR are veteran giants in the Web Framework industry. I'm sure they cover "isomorphy" in their own ways, just that at the time they were born, the terms "isomorphic" and "fullstack" weren't even coiled. This "FullSoak" framework is by no means aimed to be as full-fledged as the likes of Laravel / RoR / or even other JavaScript frameworks such as Next.js, Remix, SvelteKit, etc. - but it stays true to the "isomorphy" concept, where the same code is runnable on the browser & the server alike.

No, I found this a good explanation: https://www.lullabot.com/articles/adventures-with-edrive-accelerated-s…

It's hardly a secret tesla.com is Drupal -- both that gitignore and the robots.txt shouts it quite loudly, to be fair. One of the larger Drupal agencies, Lullabot includes them in their clients list: https://www.lullabot.com/our-work and they are looking for a sr backend Drupal engineer https://www.tesla.com/careers/search/job/sr-software-engineer-backend-… which I would take if the company were not lead by Musk.

This I can agree with. The community frowns upon selling modules. This is reflected by the official repository offering no option of purchasing modules, no marketplace. Contributors only make money by being sponsored by hosting sites like Acquia, where usually they're making modules /for/ them. This of course makes Drupal unnattractive for more advanced functionality. But, single developers still try to create that functionality anyways, even if its something that needs constant work and usual updates. This then understandably falls to the way side because life. Some things just need business behind them, they can't survive on openness alone. Also: https://www.lullabot.com/articles/why-paid-drupal-modules-fail-drupal-…

> What if the cache can parse cookies and vary the cached response by the value of a specific cookie, not the entire header? > This is caching that Varnish and other “normal” HTTP caches (including CloudFlare) could not have done. This is false. I'm not at all very familiar with Varnish, but I know this is easily possible, and has been used for many, many years. E.g. for Drupal + Varnish, i.e. to only keep Drupal's session cookie, I found these examples, in less than a minute of googling: - https://www.varnish-cache.org/trac/wiki/VarnishAndDrupal - https://www.lullabot.com/blog/article/configuring-varnish-high-availab… (grep for "inclusion") Everything in this article has been well-known for at least half a decade, yet is being presented as major technical breakthroughs. Too much marketing, IMO.

Jeff Robbins: http://www.lullabot.com/about/team/jeff-robbins I know that lots of other musicians program as well, of course, but not necessarily ostentatiously.

The BeautyTips (http://www.lullabot.com/files/bt/bt-latest/DEMO/index.html) jQuery plugin has most of these features and is quite easy to work with.

Stonebraker makes a point of saying that the lack of standards in NoSQL system prevents their adoption. While there are standards surrounding SQL most SQL databases do not adhere to the standards. They have connection semantics and syntax that are at times mutually exclusive. Drupal 7 has a dynamic query builder specifically to take care of this (see this podcast for more info http://www.lullabot.com/podcasts/drupal-voices-24-larry-garfield-new-d… But for most organizations, it's not like they can simply switch from one database system to another without a fair amount of work.

Communicating expectations / setting boundaries feels key to avoiding negativity on both sides. I recently read an article titled "Healthy Open Source Maintenance"[1], which proposed the introduction of a MAINTENANCE_MANIFESTO.md, meant to communicate expectations. Quoting the fun part: "Even though this idea is still in early stages, for the sake of clarity, this is what a selection of manifestos could look like: - The sponsor me to get priority on your bug fix manifesto. - The this is free goods and service, so you get what you get manifesto. - The micro-donations to keep the project alive, but I decide what to work on manifesto. - The hire the agency I work for to sponsor features manifesto. … The presence of the Healthy Maintainer Manifesto will be a tool to deflect social pressure. This will help maintainers that suffer from avoidance anxiety because they are not obligated to pay the maintenance taxes. Their manifesto says so! If any demanding user wants to pressure them into doing anything in particular, they can point them to the manifesto. The manifesto replaces complicated social interactions with a discharge form. The goal of this is to protect the maintainer, because, after all, maintainers are the cornerstone of open source—and thus all the software industry. And because we all prefer a community where maintainers are happy, and not at the brink of burnout." [1] https://www.lullabot.com/articles/healthy-open-source-maintenance

Glad you liked both the app and my blog! A website is down if it does not return a 200 OK HTTP status code and if the response body does not contain the text provided at registration (if such were provided). The error messages to the right are rendered out in a normal unordered list below each input. On document.ready they are retrieved with JavaScript, hidden, and copied into tool-tips provided by the BeautyTips jQuery plugin (http://www.lullabot.com/files/bt/bt-latest/DEMO/index.html). The entire service is coded in Python. The website is running Werkzeug (http://werkzeug.pocoo.org) on mod_wsgi inside Apache with Nginx as a proxy and media server in front. Jinja2 (http://jinja.pocoo.org/2/) is used for templating both the web pages and the emails. WTForms is used for form handling and validation (http://wtforms.simplecodes.com/). All data is stored in Tokyo Cabinet trough the Tokyo Tyrant network interface set up with multi-master replication. Fabric (http://www.nongnu.org/fab/) is used for deployment and other kinds of distributed automation.