4
0
Fork
You've already forked gate
0
📰 | Landing gate for ns pin points [maintainer=@orzklv]
  • HTML 34.5%
  • CSS 29.2%
  • JavaScript 23.3%
  • Nix 13%
2026年06月03日 16:06:09 +05:00
.github chore: ready presets 2025年07月22日 16:06:47 +05:00
src emergency: remove profanity 2026年05月22日 20:43:36 +05:00
.envrc chore: reviving this neggalicious project 2025年07月21日 16:58:24 +05:00
.gitignore chore: remade this shitty static web page 2025年07月22日 15:51:12 +05:00
default.nix chore: update lock + flake 2026年06月03日 16:06:09 +05:00
flake.lock chore: update lock + flake 2026年06月03日 16:06:09 +05:00
flake.nix chore: update lock + flake 2026年06月03日 16:06:09 +05:00
LICENSE chore: remade this shitty static web page 2025年07月22日 15:51:12 +05:00
package.json chore: remade this shitty static web page 2025年07月22日 15:51:12 +05:00
pnpm-lock.yaml chore: remade this shitty static web page 2025年07月22日 15:51:12 +05:00
README.md chore: ready presets 2025年07月22日 16:06:47 +05:00
shell.nix chore: update lock + flake 2026年06月03日 16:06:09 +05:00

Uzinfocom's {Gate}

Just a static website to scare off curious mamkin hackers.

Top Used Language Test CI

About

Shits happend and sometimes we get unwanted guests in our website. In that case, we decided to develop a special web page to scare off crows from our lands.

Features

  • 3D aNiMaTeD
  • Woah cool website
  • Scaaaaarry...

Development

The project has shell.nix which has development environment preconfigured already for you. Just open your terminal and at the root of this project:

# Open in bash by default
nix develop
# If you want other shell
nix develop -c $SHELL
# Upon entering development environment for the first
# time, you'll be asked for your development telegram
# bot token, it will be written to .env file for more
# convenient dev env startups. Token is saved at .env
# file at the root of this project. You can change it
# whenever you want!
# After entering development environment, inside the
# env, you can open your editor, so your editor will
# read all $PATH and environmental variables, also
# your terminal inside your editor will adopt all
# variables, so, you can close terminal.
# Neovim
vim .
# VSCode
code .
# Zed Editor
zed .

The development environment has whatever you may need already, but feel free to add or remove whatever inside shell.nix.

Building

Well, there are two ways of building your project. You can either go with classic pnpm build way, but before that, make sure to enter development environment to have pnpm and all nodejs toolchain available in your PATH, you may do like that:

# Entering development environment
nix develop -c $SHELL
# Compile the project
pnpm build

Or, you can build your project via nix which will do all the dirty work for you. Just, in your terminal:

# Build in nix environment
nix build
# Static website contents are here:
ls -lah ./result

Deploying (works only for flake based NixOS)

You have 2 ways of making use of this website.

Referring directly to packages

Import the flake in your configuration via inputs:

{
 inputs = {
 # ...
 gate.url = "github:uzinfocom-org/gate";
 };
}

and then directly refer to any arch platform via any part of your configuration:

virtualHosts = {
 "example.com" = {
 forceSSL = true;
 enableACME = true;
 root = "${inputs.gate.packages.${pkgs.stdenv.hostPlatform}}";
 };
};

Injecting via overlays

Also, you can inject this flake's package outputs into your nixpkgs packages via overlays and then make use of it as shown above!

FAQ

Why not use default.nix for devShell?

There's been cases when I wanted to reproduce totally different behaviors in development environment and production build. This occurs quite a lot lately for some reason and because of that, I tend to keep both shell.nix and default.nix to don't mix things up.

Thanks

  • Orzklv - For making this happen

License

This project is licensed under the MIT License - see the LICENSE file for details.

Uzinfocom's {Gate}