- Create repo on GitHub where you'll put your files.
- Use jsDeliver or statically to get your assets.
Here is repo I'm using:
https://github.com/jcubic/static
And links to files look like this:
You are an assistant that engages in extremely thorough, self-questioning reasoning. Your approach mirrors human stream-of-consciousness thinking, characterized by continuous exploration, self-doubt, and iterative analysis. | |
## Core Principles | |
1. EXPLORATION OVER CONCLUSION | |
- Never rush to conclusions | |
- Keep exploring until a solution emerges naturally from the evidence | |
- If uncertain, continue reasoning indefinitely | |
- Question every assumption and inference |
Here is repo I'm using:
https://github.com/jcubic/static
And links to files look like this:
#!/bin/bash | |
# Remove all settings in the .npmrc except the required auth token setting. | |
echo '//registry.npmjs.org/:_authToken=${NPM_TOKEN}' > .npmrc | |
# Create a new .yarnrc that specifies the npm registry, or append to an existing one. | |
echo 'registry: https://registry.npmjs.org/' >> .yarnrc | |
# Remove and regenerate the yarn.lock. This should be identical to running `yarn upgrade`. | |
# If you are uncomfortable regenerating the yarn.lock file, you can comment out the next |
{ | |
"useState()": { | |
"prefix": "us", | |
"scope": "javascript,javascriptreact,typescript,typescriptreact", | |
"body": [ | |
"const [${1}, set${1/(.*)/${1:/capitalize}/}] = useState($2);", | |
"$0" | |
], | |
"description": "React: useState()" | |
}, |
#!/bin/bash | |
# install qemu utils | |
sudo apt install qemu-utils | |
# install nbd client | |
sudo apt install nbd-client |
Example of deployment process which I use in my Nuxt.js projects. I usually have 3 components running per project: admin-panel SPA, nuxt.js renderer and JSON API.
This manual is relevant for VPS such as DigitalOcean.com or Vultr.com. It's easier to use things like Now for deployment but for most cases VPS gives more flexebillity needed for projects bigger than a landing page.
UPD: This manual now compatible with [email protected]. For older versions deployment, see revision history.
Let's assume that you have entered fresh installation of Ubuntu instance via SSH. Let's rock:
# Description: Boxstarter Script | |
# Author: Jess Frazelle <[email protected]> | |
# Last Updated: 2017-09-11 | |
# | |
# Install boxstarter: | |
# . { iwr -useb http://boxstarter.org/bootstrapper.ps1 } | iex; get-boxstarter -Force | |
# | |
# You might need to set: Set-ExecutionPolicy RemoteSigned | |
# | |
# Run this boxstarter by calling the following from an **elevated** command-prompt: |
Create a template service file at /etc/systemd/system/[email protected]
. The template parameter will correspond to the name
of target host:
[Unit]
Description=Setup a secure tunnel to %I
After=network.target
Warning
These guidelines haven't been updated since 2016. Learn more…
Table of contents