mirror of
https://github.com/SantaSpeen/santaspeen.ru-blog.git
synced 2026-05-19 16:10:16 +00:00
docusaurus init
This commit is contained in:
Artur Akmalov
@@ -0,0 +1,12 @@
|
||||
---
|
||||
slug: first-blog-post
|
||||
title: First Blog Post
|
||||
authors:
|
||||
name: Gao Wei
|
||||
title: Docusaurus Core Team
|
||||
url: https://github.com/wgao19
|
||||
image_url: https://github.com/wgao19.png
|
||||
tags: [hola, docusaurus]
|
||||
---
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
slug: long-blog-post
|
||||
title: Long Blog Post
|
||||
authors: endi
|
||||
tags: [hello, docusaurus]
|
||||
---
|
||||
|
||||
This is the summary of a very long blog post,
|
||||
|
||||
Use a `<!--` `truncate` `-->` comment to limit blog post size in the list view.
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
slug: mdx-blog-post
|
||||
title: MDX Blog Post
|
||||
authors: [slorber]
|
||||
tags: [docusaurus]
|
||||
---
|
||||
|
||||
Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).
|
||||
|
||||
:::tip
|
||||
|
||||
Use the power of React to create interactive blog posts.
|
||||
|
||||
```js
|
||||
<button onClick={() => alert('button clicked!')}>Click me!</button>
|
||||
```
|
||||
|
||||
<button onClick={() => alert('button clicked!')}>Click me!</button>
|
||||
|
||||
:::
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
@@ -0,0 +1,28 @@
|
||||
---
|
||||
slug: welcome
|
||||
title: Welcome
|
||||
tags: [facebook, hello, docusaurus]
|
||||
---
|
||||
Simply add Markdown files (or folders) to the `blog` directory.
|
||||
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
|
||||
|
||||
Simply add Markdown files (or folders) to the `blog` directory.
|
||||
|
||||
Regular blog authors can be added to `authors.yml`.
|
||||
|
||||
The blog post date can be extracted from filenames, such as:
|
||||
|
||||
- `2019-05-30-welcome.md`
|
||||
- `2019-05-30-welcome/index.md`
|
||||
|
||||
A blog post folder can be convenient to co-locate blog post images:
|
||||
|
||||
<!--  -->
|
||||
|
||||
The blog supports tags as well!
|
||||
|
||||
**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 55 KiB |
@@ -1,34 +0,0 @@
|
||||
---
|
||||
title: How I Leveled Up My Git Skills
|
||||
type: post
|
||||
date: 2023-01-21
|
||||
dateModified:
|
||||
tags: [git, cli, terminal]
|
||||
featuredImage:
|
||||
path: feature.jpg
|
||||
---
|
||||
|
||||
When I first started programming in git I didn't use the terminal. I had never learned how to. I had no clue where to begin, so I didn't. I searched for a gui git client and grabbed one that looked good. I also relied on source control features built into my ide. Years later that I realized how learning the cli for git how much it would improve my speed and efficiency. So here's my journey from relying on the gui to becoming comfortable in the terminal.
|
||||
|
||||
## Change Causes Evolution
|
||||
|
||||
When I first started out I wouldn't have changed my process. Until I got a new computer. Either because of old hardware or a new job. The new computer would not be set up like the old one. And thus started a long journey of remembering which apps I had installed and what settings I had for them. This was a huge pain. Which led me to stop doing it. After a few of these new set ups I stopped carrying over every app I had ever used. My git gui was one of those that didn't make. Which meant I needed a new way of running git commands.
|
||||
|
||||
## Learning as Needed
|
||||
|
||||
I started by reading the docs for git and looking up git cheat sheets. I found out that there was a lot of info out there. Too much in fact. For me, memorizing every git command wasn't going to work. Instead, I would search the internet for git commands that I needed when I ran into a need for them. It's still the way I learn how to git. I prefer it because I don't learn things that I won't need. And I learned how to git using the cli.
|
||||
|
||||
## Sanic Speed
|
||||
|
||||
The next big improvement I made was to pay attention to the aliasing the git cli brought with it. I set up my terminal so that it recognizes commands as I type them. One day I noticed that `g` was a valid command. So I ran it. Turns out `g` is an alias for `git`. So now all my `git` commands became `g` commands. And I thought this was amazing. But it gets even better! Now whenever I needed to run a git command I tried to find aliases for it. Through trial and error I figured out even the subcommands have aliases. So `git add` is the same as `ga`. But it still gets better! Turns out there are also aliases for subcommands and their flags! A common command I run is `git commit --all --message "commit message"`. And through my journey I have found these shortcuts for this same exact command:
|
||||
|
||||
- `g commit --all --message "commit message"`
|
||||
- `g commit -a -m "commit message"`
|
||||
- `gc -am "commit message"`
|
||||
- `gcam "commit message"`
|
||||
|
||||
These aliases exist for all of the subcommands I use on a daily basis: add, checkout, branch, remote, clone, push, pull, merge, status... I'm sure there are even more. I recommend using the `-h` flag on any command you use.
|
||||
|
||||
## Try It!
|
||||
|
||||
Finding these aliases has increased my speed and efficiency while programming with git. I was using the gui as a crutch to avoid the terminal and cli. I hope these aliases can help you out too.
|
||||
@@ -0,0 +1,26 @@
|
||||
---
|
||||
slug: adguard-dns
|
||||
title: Adguard DNS
|
||||
# authors: [akmalov]
|
||||
tags: [docker, homelab, linux]
|
||||
---
|
||||
|
||||
[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
|
||||
|
||||
Simply add Markdown files (or folders) to the `blog` directory.
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
Regular blog authors can be added to `authors.yml`.
|
||||
|
||||
The blog post date can be extracted from filenames, such as:
|
||||
|
||||
- `2019-05-30-welcome.md`
|
||||
- `2019-05-30-welcome/index.md`
|
||||
|
||||
A blog post folder can be convenient to co-locate blog post images:
|
||||
|
||||
|
||||
The blog supports tags as well!
|
||||
|
||||
**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.
|
||||
@@ -0,0 +1,23 @@
|
||||
endi:
|
||||
name: Endilie Yacop Sucipto
|
||||
title: Maintainer of Docusaurus
|
||||
url: https://github.com/endiliey
|
||||
image_url: https://github.com/endiliey.png
|
||||
|
||||
yangshun:
|
||||
name: Yangshun Tay
|
||||
title: Front End Engineer @ Facebook
|
||||
url: https://github.com/yangshun
|
||||
image_url: https://github.com/yangshun.png
|
||||
|
||||
slorber:
|
||||
name: Sébastien Lorber
|
||||
title: Docusaurus maintainer
|
||||
url: https://sebastienlorber.com
|
||||
image_url: https://github.com/slorber.png
|
||||
|
||||
akmalov:
|
||||
name: Artur Akmalov
|
||||
title: Docusaurus maintainer
|
||||
url: https://sebastienlorber.com
|
||||
image_url: https://github.com/slorber.png
|
||||
@@ -1,169 +0,0 @@
|
||||
---
|
||||
title: Hello World
|
||||
type: post
|
||||
date: 2023-02-21
|
||||
dateModified:
|
||||
tags: [git, cli, terminal]
|
||||
featuredImage:
|
||||
path: logo.jpg
|
||||
---
|
||||
|
||||
When I first started programming in git I didn't use the terminal. I had never learned how to. I had no clue where to begin, so I didn't. I searched for a gui git client and grabbed one that looked good. I also relied on source control features built into my ide. Years later that I realized how learning the cli for git how much it would improve my speed and efficiency. So here's my journey from relying on the gui to becoming comfortable in the terminal.
|
||||
|
||||
## The Problem
|
||||
|
||||
This is my first post on my new fake blog! How exciting!
|
||||
|
||||
I'm sure I'll write a lot more interesting things in the future.
|
||||
|
||||
Oh, and here's a great quote from this Wikipedia on
|
||||
[salted duck eggs](https://en.wikipedia.org/wiki/Salted_duck_egg).
|
||||
|
||||
> A salted duck egg is a Chinese preserved food product made by soaking duck
|
||||
> eggs in brine, or packing each egg in damp, salted charcoal. In Asian
|
||||
> supermarkets, these eggs are sometimes sold covered in a thick layer of salted
|
||||
> charcoal paste. The eggs may also be sold with the salted paste removed,
|
||||
> wrapped in plastic, and vacuum packed. From the salt curing process, the
|
||||
> salted duck eggs have a briny aroma, a gelatin-like egg white and a
|
||||
> firm-textured, round yolk that is bright orange-red in color.
|
||||
|
||||
|
||||
|
||||
You can also write code blocks here!
|
||||
|
||||
```js
|
||||
const saltyDuckEgg = "chinese preserved food product"
|
||||
```
|
||||
|
||||
| Number | Title | Year |
|
||||
| :----- | :--------------------------------------- | ---: |
|
||||
| 1 | Harry Potter and the Philosopher’s Stone | 2001 |
|
||||
| 2 | Harry Potter and the Chamber of Secrets | 2002 |
|
||||
| 3 | Harry Potter and the Prisoner of Azkaban | 2004 |
|
||||
|
||||
[View raw (TEST.md)](https://raw.github.com/adamschwartz/github-markdown-kitchen-sink/master/README.md)
|
||||
|
||||
This is a paragraph.
|
||||
|
||||
This is a paragraph.
|
||||
|
||||
# Header 1
|
||||
|
||||
## Header 2
|
||||
|
||||
Header 1
|
||||
========
|
||||
|
||||
Header 2
|
||||
--------
|
||||
|
||||
# Header 1
|
||||
|
||||
## Header 2
|
||||
|
||||
### Header 3
|
||||
|
||||
#### Header 4
|
||||
|
||||
##### Header 5
|
||||
|
||||
###### Header 6
|
||||
|
||||
# Header 1
|
||||
## Header 2
|
||||
### Header 3
|
||||
#### Header 4
|
||||
##### Header 5
|
||||
###### Header 6
|
||||
|
||||
# Header 1
|
||||
|
||||
## Header 2
|
||||
|
||||
### Header 3
|
||||
|
||||
#### Header 4
|
||||
|
||||
##### Header 5
|
||||
|
||||
###### Header 6
|
||||
|
||||
# Header 1 #
|
||||
## Header 2 ##
|
||||
### Header 3 ###
|
||||
#### Header 4 ####
|
||||
##### Header 5 #####
|
||||
###### Header 6 ######
|
||||
|
||||
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
|
||||
|
||||
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
|
||||
|
||||
> ## This is a header.
|
||||
>
|
||||
> 1. This is the first list item.
|
||||
> 2. This is the second list item.
|
||||
>
|
||||
> Here's some example code:
|
||||
>
|
||||
> Markdown.generate();
|
||||
|
||||
> ## This is a header.
|
||||
> 1. This is the first list item.
|
||||
> 2. This is the second list item.
|
||||
>
|
||||
> Here's some example code:
|
||||
>
|
||||
> Markdown.generate();
|
||||
|
||||
- Red
|
||||
- Green
|
||||
- Blue
|
||||
|
||||
* Red
|
||||
* Green
|
||||
* Blue
|
||||
|
||||
- Red
|
||||
- Green
|
||||
- Blue
|
||||
|
||||
```markdown
|
||||
- Red
|
||||
- Green
|
||||
- Blue
|
||||
|
||||
* Red
|
||||
* Green
|
||||
* Blue
|
||||
|
||||
- Red
|
||||
- Green
|
||||
- Blue
|
||||
```
|
||||
|
||||
- `code goes` here in this line
|
||||
- **bold** goes here
|
||||
|
||||
```markdown
|
||||
- `code goes` here in this line
|
||||
- **bold** goes here
|
||||
```
|
||||
|
||||
1. Buy flour and salt
|
||||
1. Mix together with water
|
||||
1. Bake
|
||||
|
||||
```markdown
|
||||
1. Buy flour and salt
|
||||
1. Mix together with water
|
||||
1. Bake
|
||||
```
|
||||
|
||||
1. `code goes` here in this line
|
||||
1. **bold** goes here
|
||||
|
||||
```markdown
|
||||
1. `code goes` here in this line
|
||||
1. **bold** goes here
|
||||
```
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 668 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 51 KiB |
@@ -1,46 +0,0 @@
|
||||
---
|
||||
title: React Native Environment Setup
|
||||
type: post
|
||||
date: 2023-04-24
|
||||
dateModified:
|
||||
tags: [react, setup, env, config]
|
||||
featuredImage:
|
||||
path: feature.jpg
|
||||
---
|
||||
|
||||
I enjoy building apps in react native. Yet, configuring my system to run them is a pain. In this article I'll outline how I've tried to make it less painful.
|
||||
|
||||
## Node
|
||||
|
||||
React native uses node to interface with the native JS runtime on Android and iOS. The runtime allows for hooks into native code which is how we can build high performing native apps.
|
||||
I use NVM to manage my node installs. It lets me manage many versions for various projects.
|
||||
|
||||
## Watchman
|
||||
|
||||
React native uses watchman to watch changes, compile, and refresh the app on your device. I install this from brew; no management required.
|
||||
|
||||
## Ruby
|
||||
|
||||
React native needs ruby to use CocoaPods (a ruby gem) for handling iOS dependencies. I started out using rvm but have since switched to rbenv. Both libraries allow managing ruby version. I found rbenv much easier to set up than rvm.
|
||||
|
||||
## Xcode
|
||||
|
||||
React native needs Xcode for iOS development tooling including the iOS simulator. For a while I installed this via the Mac App Store but downloads took forever and sometimes got stuck. I have switched to using Xcodes to manage having many versions of Xcode installed. Downloads don’t take as long and have not gotten stuck thus far.
|
||||
|
||||
## JDK
|
||||
|
||||
React native needs a JDK for Android development. I use jenv to manage jdk versions and prefer openJDKs. I grab openJDKs from brew and add them into jenv.
|
||||
|
||||
## Android Studio
|
||||
|
||||
React native needs Android Studio for Android development tooling. During install include Android SDK, Android SDK Platform, and Android Virtual Device. The latest Android SDK installs by default. Check that it's compatible with the version of react native you’re using. You can use the SDK Manager within Android Studio to install the correct version. In order for react native to build apps with native code some environment variables need set up.
|
||||
|
||||
```
|
||||
export ANDROID_HOME=$HOME/Library/Android/sdk
|
||||
export PATH=$PATH:$ANDROID_HOME/emulator
|
||||
export PATH=$PATH:$ANDROID_HOME/platform-tools
|
||||
```
|
||||
|
||||
## Create An App
|
||||
|
||||
At this point the system is set up to run react native applications. There are several options for spinning up a new react native app. I have used the CLI to create apps with and without expo. I have also used a 3rd party CLI called Ignite from InfiniteRed. My next project will use a template from TheCodingMachine called React Native Boilerplate.
|
||||
Reference in New Issue
Block a user