Supabase - ~52K stars
- Designed explicitly as an open source firebase alternative
- Typescript based
- Docker support
Appwrite - ~32K stars
- Written in JavaScript and PHP
- Docker based
- Realtime support across all services
# this file contains keys needed for decryption of file system data (WUD/WUX) | |
# 1 key per line, any text after a '#' character is considered a comment | |
# the emulator will automatically pick the right key | |
541b9889519b27d363cd21604b97c67a # example key (can be deleted) | |
d7b00402659ba2abd2cb0db27fa2b656 # Common | |
805e6285cd487de0faffaa65a6985e17 # Espresso Ancast | |
b5d8ab06ed7f6cfc529f2ce1b4ea32fd # Starbuck Ancast | |
9a164ee15ac7ceb64d3cc130094095f6 # 007 Legends [EUR, NUS] |
The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.
Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.
This repo also contains a bundled version of npm that has a new command, asset
. You can read the documentation for and goals of that comma
/** | |
* This is an experiment for testing the "Concurrency Model and Event Loop" of | |
* JavaScript. | |
* | |
* It's designed that an asynchronous function with a given callback is called; | |
* And subsequently a synchronous function which is designated to take far more | |
* time than the asynchronous one will take is called. | |
* | |
* Question: what is the response order of async-fun/sync-fun/callback? | |
* |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
//Custom Theme test | |
// Colors | |
// ------------------------------- | |
$custom: #057b6c !default; | |
// Buttons | |
// ------------------------------- | |
$button-custom-bg: $custom !default; |
<VirtualHost *:80> | |
DocumentRoot "/Users/arpaul/Sites/school/public" | |
ServerName school.dev | |
<Directory "/Users/arpaul/Sites/school/public"> | |
Options FollowSymLinks Indexes MultiViews | |
AllowOverride All | |
</Directory> | |
</VirtualHost> |
The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.
You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.
#!/bin/bash | |
# ~/.bashrc | |
# | |
# | |
# shosei | |
# Shell Init | |
[[ $PATH = *local/bin* ]] || PATH=$PATH:/usr/local/bin | |
[[ $- = *i* ]] || return |