Skip to content
University of Hilla / AI & Cybersecurity Club

A Linux workspace in a browser tab. It keeps your files between sessions.

Sign in, open your project, use the terminal and Git, then start a server and reach it over HTTPS. There is nothing to install, and the same directory is waiting for you next session.

  • Nothing to install
  • Files kept between sessions
  • HTTPS previews
web-lab / project running
PROJECT
  • app.js
  • index.html
  • README.md
  • .git
cd ~/projects/web-lab
npm run dev
vite v5.4.2 ready in 384 ms
Local: http://0.0.0.0:3000/
port 3000 is now reachable over https
preview https://3000--main--web-lab--student.shamashcyber.com
~/projects/web-labrunning
cd ~/projects/web-lab
npm run dev
vite v5.4.2 ready in 384 ms
Local: http://0.0.0.0:3000/
port 3000 is now reachable over https
files3
app.jsedited now
README.mdsaved
.gitclean
previewhttps
port3000
https://3000--main--web-lab--student.shamashcyber.com
What a running app looks like

https://3000--main--web-lab--student.shamashcyber.com

  1. port3000
  2. branchmain
  3. workspaceweb-lab
  4. userstudent

You start a server on port 3000 inside your workspace. ShamashCyber gives that port its own HTTPS address, scoped to your session. Port 3000 is never opened on the host.

What you get

Four things, and they are the same four every session.

  • ~/projects

    Files stay put

    Stopping a session does not delete your work. Start again and the directory is the way you left it, with the same files and the same history.

  • bash

    A real Linux shell

    Package managers, compilers, scripts and development servers. Not a simulated terminal and not a sandbox that resets on refresh.

  • git

    Git where the code runs

    Clone, branch, commit and push from the session you are building in, instead of copying the project between machines.

  • :3000

    Ports become addresses

    Any port your application listens on can be opened as an HTTPS address that belongs to your session and nobody else's.

How it fits together

One session, four layers deep.

The student sees one browser tab. Behind it the session, the stored project and the preview route stay separate, which is what lets a workspace stop without the work stopping with it.

One session

Four moves, and no setup between them.

The workspace, the shell, the repository and the preview are views of one session. Nothing is handed off to a second service in the middle.

01

Sign in

Open the workspace portal in any modern browser. This is the only entry point.

workspace.shamashcyber.com
02

Open the project

Your home directory is already there. Move into the project you were working on.

cd ~/projects/web-lab
03

Run it

Install dependencies and start the development server from the terminal in the same session.

npm run dev
04

Open the preview

Open the port from the workspace interface. The running app gets an HTTPS address.

3000 → https
Who it is for

Built for practical work, not for demonstrations.

ShamashCyber is used for programming labs, technical workshops and student projects. It exists because lab time was going into fixing environments instead of writing code.

  • University of Hilla

    Programming labs and coursework, where every student needs the same environment and the same tools on whatever machine is free that day.

  • AI & Cybersecurity Club

    Workshops, experiments and club projects, including work that is easier to run in an isolated environment than on a personal laptop.

Open a workspace and put something on a port.

The fastest way to understand it is to run one small project end to end. The docs walk through it in about five minutes.