Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.

I won a Samsung Galaxy S6 Edge, signed into it with my Google account, played around with it, wiped it, and sold it. Now the person can't get past setup because it's saying he must login with an a...

Upgrade from 0.6.5 to 0.8.4 (ArchLinux AUR version).

As others have recommended in comments, it looks like the canonical way to test Express controllers is through supertest.

An example test might look like this:

describe('GET /users', function(){
  it('respond with json', function(done){
    request(app)
      .get('/users')
      .set('Accept', 'application/json')
      .expect(200)
      .end(function(err, res){
        if (err) return done(err);
        done()
      });
  })
});

Upside: you can test your entire stack in one go.

Downside: it feels and acts a bit like integration testing.

A Test-Anything-Protocol library for Node.js

<VirtualHost example.com:*>
  ProxyPreserveHost On

  ProxyPass /api http://localhost:3000/
  ProxyPassReverse /api http://localhost:3000/

  ServerName localhost
</VirtualHost>

Une BiblioBox est une LibraryBox, déclinaison de la PirateBox. Il s’agit d’un dispositif de partage de ressources numériques (livres électroniques, vidéos, musiques, logiciels, photos, ect..).

La BiblioBox génère un réseau auquel on se connecte en wifi via un smartphone, une tablette ou un ordinateur portable puis on télécharge les contenus disponibles. Sous le capot, c'est des logiciels libres

LibraryBox is an open source, portable digital file distribution tool based on inexpensive hardware that enables delivery of educational, healthcare, and other vital information to individuals off the grid.

Mastoshare - Un bouton de partage social pour Mastodon

Open your Shaarli and Login
Click the Tools button in the top bar
*Click the ✚Add to Firefox social button and accept the activation.

• Software etymologist (traces the genealogy of terms, processes, ideas, and systems)

• Software entomologist (classifies bugs and studies their behavior; offshoot of security research)

• Software ecologist (studies the interactions of vast numbers of huge, ancient systems)

• Software zoning manager (controls what software is allowed to exist based on concerns about stability raised by software ecologists & software historians)

<p>Job titles of the near future:</p><p> Software gardener (the intersection of devops & maintenance)</p><p> Software archaeologist (maintenance of old but important systems)</p><p> Software anthropologist (maintenance of old but important systems whose behavior is confusing)</p><p> Software documentary editor (a software anthropologist that annotates old broken software & its documentation for software historians)</p><p>* Software historian (studies old versions of software to make it understandable to modern users)</p>

One of the things that really got me on board with NodeJS was the idea that I didn’t need a host container for it. Building a web app just means including a library that listens for HTTP requests on a port and respond. No more Apache! One less thing to worry about that isn’t my app!

And then it starts getting complicated.

For a start, port 80 is a privileged port, so when you try to launch the app to test or develop on your own machine you need to do so with sudo. That’s a little annoying, but you could default to port 80 & allow an override. But now you are adding more code to workaround it.

And what about SSL? If you are going to use SSL in production (and you should) then your code is going to have to know about that too and read the certs and set that up. And that’s even more annoying for development, anyone working on your code is going to have to create their own certs just to launch your app. Unless you code in more workarounds.

So that’s a suddenly a lot of code you are maintaining which might create its own problems.

The alternative … use a webserver as a proxy for your app in production. It doesn’t have to be Apache, you could use Nginx for example. I use Apache because I’m reasonably familiar with it.