Loïc Liné twysto

## dipl.io.conf
server {
	listen 80 default_server;
	listen [::]:80 default_server ipv6only=on;
	server_name www.dipl.io dipl.io;
	return 301 https://dipl.io$request_uri;
}

server {
    listen 443 ssl http2;
	listen [::]:443 ssl http2;

## README.md

      
              1 file
            
          
              30 forks
            
          
              15 comments
            
          
              215 stars
            
          
                renchap
                / README.md
            
            
              Last active
              October 12, 2022 17:14
            
              
                One-line certificate generation/renews with Letsencrypt and nginx
              
          
    Prerequisites : the letsencrypt CLI tool
This method allows your to generate and renew your Lets Encrypt certificates with 1 command. This is easily automatable to renew each 60 days, as advised.
You need nginx to answer on port 80 on all the domains you want a certificate for. Then you need to serve the challenge used by letsencrypt on /.well-known/acme-challenge.
Then we invoke the letsencrypt command, telling the tool to write the challenge files in the directory we used as a root in the nginx configuration.
I redirect all HTTP requests on HTTPS, so my nginx config looks like :
server {


## meteor-windows-vagrant-tutorial.md

      
              1 file
            
          
              25 forks
            
          
              39 comments
            
          
              93 stars
            
          
                gabrielhpugliese
                / meteor-windows-vagrant-tutorial.md
            
            
              Last active
              April 19, 2022 14:37
            
              
                Tutorial for running Meteor in Windows using Vagrant
              
          
    Tutorial: Meteor in Windows using Vagrant

BEFORE YOU CONTINUE:

Now, Meteor runs in any Windows without any line of this tutorial. Just download the Meteor binary! Yay!!
mrt is no longer used with Meteor 1.0

These days some people were discussing at meteor-talk group about running Meteor at Windows and I’ve recommended them using Vagrant. It’s a very developer-friendly piece of software that creates a virtual machine (VM) which let you run any operating system wanted and connect to it without big efforts of configuration (just make the initial installation and you have it working).
Many packages (I've tested) for running Meteor+Vagrant fails because Meteor writes its mongodb file and also other files inside local build folder into a shared folder between the Windows host and the Linux guest, and it simply does not work. So I've put my brain to work and found a solution: do symlinks inside the VM (but do not use ln. Use mount so git can follow it). It’s covered on

  
## js-frameworks.md

      
              1 file
            
          
              1 fork
            
          
              3 comments
            
          
              14 stars
            
          
                clarle
                / js-frameworks.md
            
            
              Created
              August 19, 2012 16:54
            
              
                Mojito/Derby/Meteor comparison (Public WIP)
              
          
    Next-generation JavaScript frameworks

Web application frameworks have been developing fast in the past few years, and as the technologies that they're built on top of get more advanced, each of these frameworks is able to provide newer features to help developers build more complex applications.  This year, we've seen the release of a new class of application frameworks that takes advantage of JavaScript's ability to be both on the client and the server.  What this allows these frameworks to do is provide both a new level of abstraction by sharing code between client and server, as well as embrace the benefits of both client-side rendering and server-side rendering.
For the end user, they get smooth, desktop-like responsiveness from client-side rendering, while still being able to maintain the SEO and accessbility benefits of server-side rendering.  For developers, that means writing less boilerplate code, and being able to focus more on writing the application logic.
Today, there are three main framew

  
## ios-8-web-app.html
<!doctype html>

<!-- http://taylor.fausak.me/2015/01/27/ios-8-web-apps/ -->

<html>
  <head>
    <title>iOS 8 web app</title>

    <!-- CONFIGURATION -->
	server {
	listen 80 default_server;
	listen [::]:80 default_server ipv6only=on;
	server_name www.dipl.io dipl.io;
	return 301 https://dipl.io$request_uri;
	}

	server {
	listen 443 ssl http2;
	listen [::]:443 ssl http2;
	<!doctype html>

	<!-- http://taylor.fausak.me/2015/01/27/ios-8-web-apps/ -->

	<html>
	<head>
	<title>iOS 8 web app</title>

	<!-- CONFIGURATION -->