Skip to content
10x Resume

Testing publication

10x Resume candidates can use the just ↗︎ commands described below to test how their published content appears when served by their local development server.

Testing published content

Steps

  1. To test the published content, start the local 10x Resume development server by running the following command from the git worktree (e.g. ~/10xresume/34476472.Brilliant)

    Terminal window
    just dev
    Sample output
    % just dev
    pnpm install --reporter=append-only
    Scope: all 24 workspace projects
    Lockfile is up to date, resolution step is skipped
    Already up to date
    

    Done in 1.6s
    [ ! -e .env ] && cp .env.local .env
    [ ! -e $(dotenvx get ENCFILE) ] && just write-enc
    pnpm run dev
    

    > 10xresume@ dev /Users/demo/10xresume/34476472.Company
    >                dotenvx run -- turbo dev    --concurrency=12
    

    [dotenvx@1.19.2] injecting env (19) from .env
    turbo 2.3.3
    

    • Packages in scope: @repo/Access, @repo/Access-browser, @repo/Access-node, @repo/App, ...
    • Running dev in 23 packages
    • Remote caching disabled
    @repo/Codeview:dev: cache bypass, force executing 608b110fb4448f52
    @repo/Details-render:dev: cache bypass, force executing a9d5e87044119454
    @repo/App:dev: cache bypass, force executing 3908eec8c134a5fe
    @repo/Pdf:dev: cache bypass, force executing d61dc7f31b74d236
    @repo/Cli:dev: cache bypass, force executing 65f1412d431bbfaf
    @repo/Access-browser:dev: cache bypass, force executing 7621e9b98452a953
    @repo/Portfolio:dev: cache bypass, force executing 6324f2bcbfcff071
    @repo/Details:dev: cache bypass, force executing 28a1efd00f7b8001
    @repo/Details-css:dev: cache bypass, force executing 43d2996860f5588f
    @repo/Access:dev: cache bypass, force executing 595ca207110ea032
    @repo/Cache:dev: cache bypass, force executing 6b38359e578d9240
    @repo/Codeview:dev:
    @repo/Codeview:dev: > @repo/Codeview@ dev /Users/demo/10xresume/34476472.Company/Packages/Codeview
    @repo/Codeview:dev: > tsc --watch
    @repo/Codeview:dev:
    ...
    @repo/App:dev: [0] 4:27:49 PM - Starting compilation in watch mode...
    @repo/Details-render:dev: > @repo/Details-render@ render /Users/demo/10xresume/34476472.Company/Packages/Details-render
    @repo/Details-render:dev: > dotenvx run -f ../../.env -- node dist/Render.cjs
    @repo/App:dev: [1]   VITE v5.4.11  ready in 882 ms
    @repo/App:dev: [1]
    @repo/App:dev: [1]   ➜  Local:   https://localhost:5173/
    @repo/App:dev: [1]   ➜  Network: https://169.254.33.19:5173/
    @repo/App:dev: [1]   ➜  Network: https://192.168.1.51:5173/
    @repo/Details-render:dev: [dotenvx@1.19.2] injecting env (19) from ../../.env
    @repo/App:dev: [1] /
    @repo/App:dev: [1] /?34476472
    @repo/Details-render:dev: Wrote ../../Job/Pdf/Src/_includes/details.html
    @repo/Details-render:dev: Wrote ../../Job/Pdf/Src/_includes/details.css
    @repo/Details-render:dev: [nodemon] clean exit - waiting for changes before restart
    @repo/Pdf:dev: [11ty] File changed: Src/_includes/details.css
    @repo/Pdf:dev: [11ty] File changed: Src/_includes/details.html
    @repo/Pdf:dev: [11ty] Writing ./build/index.html from ./Src/index.njk
    @repo/Pdf:dev: [11ty] Copied 17 Wrote 1 file in 0.03 seconds (v3.0.0)
    @repo/Pdf:dev: [11ty] Watching…
    @repo/Access:dev: [4:27:50 PM] Found 0 errors. Watching for file changes.
    @repo/App:dev: [1] /index.tsx
    @repo/App:dev: [1] /App.tsx
    @repo/App:dev: [1] /DOTENV.json?import
    @repo/Pdf:dev: Prince ok
    @repo/Access-browser:dev: [4:27:56 PM] Found 0 errors. Watching for file changes.
    @repo/Cache:dev: [4:27:57 PM] Found 0 errors. Watching for file changes.
    @repo/Cli:dev: [0] 4:27:58 PM - Found 0 errors. Watching for file changes.
    @repo/Codeview:dev: [4:28:00 PM] Found 0 errors. Watching for file changes.
    @repo/App:dev: [0] 4:28:05 PM - Found 0 errors. Watching for file changes.

    Eventually a message of the form

    @repo/App:dev: [0] ... - Found 0 errors. Watching for file changes.

    will appear indicating that the server is ready

  2. In another terminal, run the following command from the git worktree to display the link and password to access the content:

    Terminal window
    just link

    Sample output

    Terminal window
    % just link
           link https://localhost:5173/?00000000#/l/7cCwTvv93tpJhnU44MwMuA
    static link https://localhost:5173/static?00000000#/l/7cCwTvv93tpJhnU44MwMuA
       password xxxxxxxxxxxxxxxxxxxx

    On OSX, the following command will copy the password to the clipboard and open the 10x Resume static development link in a browser.

    Terminal window
    just openlink