These are my software stacks broken down by category.
Category | Languages | Libraries | Tools |
---|---|---|---|
Server | Elixir | Ecto, Phoenix | Credo |
Web | TypeScript | React | ESLint, Prettier |
CLI | Go |
// ==UserScript== | |
// @name Poker Now HUD | |
// @namespace http://j1.io/ | |
// @version 0.1 | |
// @description HUD for Poker Now | |
// @author You | |
// @match https://www.pokernow.club/games/* | |
// @icon https://cdn.pokernow.club/favicon-cd2bc2773f4f49ce85f0.png | |
// @grant none | |
// ==/UserScript== |
// SPDX-License-Identifier: MIT | |
pragma solidity ^0.7.5; | |
/** | |
* @dev Collection of functions related to the address type | |
*/ | |
library Address { | |
/** | |
* @dev Returns true if `account` is a contract. | |
* |
// SPDX-License-Identifier: MIT | |
pragma solidity ^0.6.2; | |
/** | |
* @dev Collection of functions related to the address type | |
*/ | |
library Address { | |
/** | |
* @dev Returns true if `account` is a contract. | |
* |
Meteor is an amazing full-stack framework which integrates MongoDB into it's DDP model. However, Meteor is closely integrated between it's different components, which makes it hard to modify its stack sometimes. Today, I'm going to demonstrate a simple trick to allow you to use your Meteor app with an external Mongo database, making it easier to integrate your Meteor app with other apps and data processing functions. This tutorial will even work with Meteor's regular DDP model, allowing for the continuation of the usual hot-reload upon data changes.
First, we need to set up the database on the server side. If you are using Meteor 1.3, you should place this code inside the /server
directory of your app. It will be automatically loaded into the server.
var database = new MongoInternals.RemoteCollectionDriver('mongodb://user:password@localhost:27017/myapp')
The most important thing I've learned from years of using Linux is how to troubleshoot problems. I've compiled a list of the most useful tips for fixing almost any Linux problem. Please enjoy but use these at your own risk!
chmod
Everything
Your first step should be to give everything in sight permission to execute. This will allow any shy processes their fair share of your server. Try it out: chmod -R 777
setenforce 0
And there you have it, you've successfully solved 99% of Linux problems! Congratulations, Bobby Tables, you did it!
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
I hereby claim:
To claim this, I am signing this object: