$ export ECS_CLUSTER_NAME={YOUR_ECS_CLUSTER_NAME}
$ export ECS_SERVICE_NAME={YOUR_ECS_SERVICE_NAME}
/* | |
usage: | |
--- | |
a.link { | |
@include underline(red, 1px, 5px, true) | |
} | |
--- | |
above renders a red 'underline' with a 1px width, offsetted 5px from the bottom of |
class ColumnBuilder extends StatelessWidget { | |
final IndexedWidgetBuilder itemBuilder; | |
final MainAxisAlignment mainAxisAlignment; | |
final MainAxisSize mainAxisSize; | |
final CrossAxisAlignment crossAxisAlignment; | |
final TextDirection textDirection; | |
final VerticalDirection verticalDirection; | |
final int itemCount; |
There are times when you need to log off your Linux Desktop, and you want a process to run in the background. TMUX manages this very well.
For this example, let's suppose you're running a long running task like running rspecs
on your project and
it is 5pm, and you need to go home.
// Usually I use this in my app's config file, in case I need to disable all cache from the app | |
// Cache is from `js-cache`, something like `import Cache from 'js-cache';` | |
const cacheable = true, | |
cache = new Cache(); | |
// On request, return the cached version, if any | |
axios.interceptors.request.use(request => { | |
// Only cache GET requests | |
if (request.method === 'get' && cacheable) { |
To reduce the number of chunks of your project build with Nuxt.js add the next lines:
if (!this.dev) {
config.plugins.push(new webpack.optimize.LimitChunkCountPlugin({
maxChunks: 3
}))
}
right under extend (config, ctx) {
of nuxt.config.js
.
Then build your project with npm run build
. Et voilà, No more than 3 chunks :-)
#!/bin/bash | |
fdisk -lu | |
pvscan | |
vgscan | |
vgchange -a y | |
lvscan | |
mount /dev/ubuntu-vg/root /mnt | |
mount --bind /dev /mnt/dev | |
mount --bind /proc /mnt/proc |
ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key | |
# Don't add passphrase | |
openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub | |
cat jwtRS256.key | |
cat jwtRS256.key.pub |
Mosh (mobile shell) is a gift from the Gods(tm). Anyone with spotty internet or wireless connection has suffered the pain of a lost SSH session. Sure, one can fire up screen
(or tmux
as the kids are using these days), but that's an extra step and you are still using the SSH protocol.
I'm not here to tout the benefits of Mosh, you came here to open it up in your firewall.
- Create the following file as
/etc/firewalld/services/mosh.xml
firewall-cmd --add-service=mosh --permanent
firewall-cmd --reload
If you tend to have a lot of sessions (not recommended), you can increase the ports, but the default should be fine for most applications.