hAbuMustafa

"workbench.editor.customLabels.patterns": {
  // The main content for the whole website
  "**/src/routes/+page.svelte": "Main Page", // The home route page skeleton
  "**/src/routes/+page.[tj]s": "Main Page Script (c)", // The script for it
  "**/src/routes/+page.server.[tj]s": "Main Page Script (s)", // The server script for it

  "**/src/routes/+layout.svelte": "Root Layout", // The main (root) layout for the website
  "**/src/routes/+layout.[tj]s": "Root Layout Script (c)", // The client script associated with the whole website
  "**/src/routes/+layout.server.[tj]s": "Root Layout Script (s)", // The server script associated with the whole website
  // Root error pages

belgattitude

Why

Although @setup/node as a built-in cache option, it lacks an opportunity regarding cache persistence. Depending on usage, the action below might give you faster installs and potentially reduce carbon emissions (♻️🌳❤️).

Requirements

Yarn 3+/4+ with nodeLinker: node-modules. (Not using yarn ? see the corresponding pnpm 7/8+ action gist)

Structure

danielstrelec

# nastaveni ftp serveru
variables:
  # devel server
  FTP_DEV_URL: "***"
  FTP_DEV_USERNAME: "***"
  FTP_DEV_PASSWORD: "***"
  # produkce
  FTP_PROD_URL: "***"
  FTP_PROD_USERNAME: "***"
  FTP_PROD_PASSWORD: "***"

danielstrelec

# nastaveni ftp serveru
variables:
  FTP_URL: "***"
  FTP_USERNAME: "***"
  FTP_PASSWORD: "***"

deploy:
  # nazev akce
  stage: deploy
  # natazeni docker image s git-ftp